Every reseller store gets its own Meta Pixel, Conversions API and TikTok tracking
Each reseller pastes their own Pixel ID and access token once. From then on, every view, add to cart and confirmed order on their store is sent to their own ad account, from the browser and from the server.
- Own Meta Pixel per store
- Meta Conversions API
- TikTok Pixel and Events API
- Event ID deduplication
- Standard events mapped
EOMS BD builds reseller and dropshipping platforms in Bangladesh where every reseller store can connect its own Meta Pixel, Meta Conversions API and TikTok Pixel with TikTok Events API. Each reseller enters their own IDs in their panel, so the sales from their ads are reported to their own ad account, not the platform owner's. This lets platform owners offer resellers proper ads tracking without manual code work for every store.
প্রতিটি রিসেলার স্টোরে আলাদা ফেসবুক পিক্সেল ও কনভার্সন API
EOMS BD বাংলাদেশে এমন রিসেলার ও ড্রপশিপিং প্ল্যাটফর্ম তৈরি করে যেখানে প্রতিটি রিসেলার নিজের প্যানেল থেকে নিজের Meta Pixel, Conversions API এবং TikTok Events API যুক্ত করতে পারেন। ফলে কোন বিজ্ঞাপন থেকে কোন অর্ডার এলো, তা রিসেলারের নিজের অ্যাড অ্যাকাউন্টে দেখা যায়। প্ল্যাটফর্ম মালিককে প্রতিটি স্টোরে আলাদা করে কোড বসাতে হয় না।
Why ads tracking breaks on most reseller platforms
Resellers in Bangladesh mostly sell through Facebook and TikTok ads. If the platform cannot tell their ad account which visit became an order, they are boosting posts blind and the platform loses its best sellers.
One Pixel for the whole platform
Many platforms install a single Pixel owned by the admin. Resellers running their own ads see no purchases in Ads Manager and cannot tell which ad worked.
Browser-only tracking misses events
Ad blockers, in-app browsers and privacy settings stop many browser Pixel events. Without a server-side connection, reported purchases can be far lower than real orders.
Duplicate or fake purchase events
When the same order fires twice, or a Purchase event fires on order placement and is never cancelled on return, ad reports look better than the business really is.
Manual code for every store
Asking a developer to paste scripts into hundreds of reseller stores is slow, error-prone and impossible to maintain when Meta or TikTok change their requirements.
See who sees which numbers
This live dashboard shows orders, sales, profit and returns with sales vs cost bars. Use the role switcher to view it as Admin, Reseller or Staff: the reseller view shows only that store's numbers, the same data their own ad tracking is based on. All figures are sample data.
- Own Meta Pixel per store
- Meta Conversions API
- TikTok Pixel and Events API
- Event ID deduplication
Sample data — your platform shows your real numbers.
Everything your website will do
Own Meta Pixel per store
Each reseller adds their own Pixel (dataset) ID in their panel. Events from their store go to their ad account, and the platform owner can keep a separate master Pixel.
Meta Conversions API
Key events are also sent from the server using the reseller's access token, so purchases are still reported when the browser Pixel is blocked.
TikTok Pixel and Events API
Resellers who advertise on TikTok can connect their TikTok Pixel and Events API token the same way, with the same events mapped automatically.
Event ID deduplication
Browser and server copies of each event carry the same event ID, so Meta and TikTok can count one order once instead of twice.
Standard events mapped
View content, add to cart, initiate checkout and purchase are fired at the right steps, with product ID, value in BDT and quantity included.
Choose when Purchase fires
The platform owner decides whether Purchase is sent on order placement or after phone confirmation, which helps keep fake COD orders out of ad reports.
Hashed customer data
Phone numbers and emails sent for matching are hashed as Meta and TikTok require, and tokens are stored encrypted and never shown to other resellers.
Connection status check
Each reseller sees whether their Pixel and API connection is active, with a test-event option, so support teams can fix setup issues quickly.
From first call to launch in 5 steps
Tracking plan
We agree which events to track, when Purchase should fire, and whether the platform owner also keeps a master Pixel across all stores.
Reseller settings screen
We add fields in the reseller panel for Meta Pixel ID, Conversions API token, TikTok Pixel ID and Events API token, with simple help text.
Browser and server events
We wire browser Pixel events and server-side API calls into the store, checkout and order flow, sharing one event ID for deduplication.
Testing with real accounts
We test with Meta Events Manager and TikTok Events Manager test tools, checking that events arrive once with correct values in BDT.
Training and support
We train your support team and record a short tutorial for resellers, then provide 6 months free support and 1 year of free bug fixing.
Per-store tracking vs a single shared Pixel
| Feature | With EOMS BD | Typical setup |
|---|---|---|
| Whose ad account gets the data | Each reseller's own account | Only the admin's Pixel |
| Server-side events | Meta Conversions API and TikTok Events API | Browser Pixel only |
| Duplicate purchases | Shared event ID for deduplication | Often counted twice |
| When Purchase is sent | Owner's choice, e.g. after confirmation | On every placed order, fake or not |
| Adding a new store | Reseller pastes IDs in panel | Developer edits code |
| Setup visibility | Connection status per store | Nobody knows if it works |
Frequently asked questions
Yes. On a platform built by EOMS BD, every reseller store has its own settings where the reseller pastes their Meta Pixel ID. Events from that store go to that reseller's ad account only. The platform owner can also keep a master Pixel to see activity across all stores.
The Conversions API is Meta's way of sending events from your server instead of only from the visitor's browser. Browser Pixel events are often lost to ad blockers, in-app browsers and privacy settings. Sending purchases from the server as well gives Meta a more complete picture, which matters when resellers rely on ad reports to decide where to spend.
Yes. Resellers can connect a TikTok Pixel and a TikTok Events API access token in the same settings screen. The same store events are mapped for TikTok, with an event ID shared between browser and server copies so TikTok can deduplicate them.
No. Correct tracking gives resellers accurate data and helps Meta and TikTok optimise delivery, but ad results still depend on the product, price, creative, audience and budget. EOMS BD sets up the tracking properly; it does not promise sales, lower cost per order or any specific return on ad spend.
The platform owner can choose to send the Purchase event only after an order is confirmed by phone or by the fraud check, instead of at checkout. That keeps unconfirmed and fake orders out of the reseller's ad reports. Order confirmation itself is covered on our order and return control page.
Per-store ads tracking is usually built as part of the full reseller platform, which typically takes 4 to 8 weeks depending on modules. Adding this module to an existing EOMS BD platform is shorter. We confirm the timeline after the free consultation.
Yes, 100%. The domain, hosting, source code and database belong to you. Each reseller's Pixel and API tokens stay in your database, encrypted, and you can extend the tracking with any developer later.
Build the complete system
Give every reseller ads tracking that works
Book a free demo with EOMS BD and see how per-store Meta Pixel, Conversions API and TikTok Events API work on a reseller platform. Call or WhatsApp +880 1784-222255 or email info@eomsbd.com.
+880 1784-222255info@eomsbd.com · Dhaka, Bangladesh