Dukun Ads

Tracking & ads10 min/sales

DukunTrack: install tracking and read your analytics

One script tag gives you sessions, sources, scroll depth, conversions and revenue split by paid vs free traffic.

Last reviewed 2026-07-20

DukunTrack is the analytics layer for pages you own. One script tag records who visits, where they came from, how far they scrolled, where they left, and what they bought — and splits revenue into traffic that cost you ad money versus traffic that did not.

The same snippet also installs your Meta Pixel and sends server-side conversions, so you install one thing rather than three. Everything below lives at /sales.

Step by step

  1. Register the page you want to track

    Press + Add sales page, then fill in a Name (something you will recognise, like VitC Serum Landing) and the Sales page URL.

    This works for any page you control — a landing page, a bridge page for affiliate links, a link-in-bio page, a checkout page.

  2. Attach a Meta Pixel

    You have three options, in order of preference:

    1. 🔗 Pick a pixel from Meta Ads — if you have connected a Meta Ads account, your existing pixels are listed, grouped by ad account. Choosing one here means server-side conversions are sent automatically and no access token is needed.
    2. ➕ Create a new pixel — pick an ad account, give the pixel a name, and it is created for you.
    3. Enter it manually — paste a Meta Pixel ID, and optionally a CAPI access token from Events Manager → Settings → Conversions API for server-side tracking.

    Press Save. If you have no pixel at all, you can still save the page and get visitor analytics — the pixel only affects what Meta receives.

  3. Install the snippet

    Your saved page now shows an install block. Copy the script tag and paste it inside the <head> of your website:

    Paste inside <head>
    <script src="https://dukunads.com/api/track/…" async></script>

    Copy the exact tag from your own page — it contains the tracking key that identifies your site. One tag installs both the Meta Pixel and the visitor tracking. Put it in the <head>, not before </body>, so it captures the pageview and the ad click ID on arrival.

  4. Record conversions

    Pageviews are tracked automatically. To record a sale, call the tf function — from your thank-you page, your checkout success handler, or manually when you close a deal in chat:

    tf('Purchase', {
  value: 89,
  currency: 'MYR',
  email: 'customer@email.com'
});

    Always include a real value and currency, otherwise ROAS is meaningless. The email is hashed before it is sent and dramatically improves how well Meta can match the conversion to a real person.

  5. Verify it is working

    Open your page in a normal browser window, then come back to /sales and press Quick view on the card. Within a minute you should see at least one session.

    If nothing appears: check the snippet is actually in the served HTML (view source, not just your editor), check that a browser extension is not blocking it, and confirm you copied the tag from the right page.

  6. Read the quick view

    Quick view gives you the last 30 days at a glance: sessions, unique visitors, conversion rate, revenue, bounce rate, average scroll depth and average time on page, plus breakdowns by traffic source and device, conversions by source, and a table of recent events.

    This is the right level of detail for a daily check.

  7. Read the full analytics

    Press 📊 Full analytics to open the detailed view. Pick a period — today, yesterday, last 7 / 30 / 90 days, this month, last month, this year, all time, or a custom range — and work down the page:

    • Overview — sessions, unique visitors, pageviews, conversions, conversion rate, revenue, average scroll, average time, bounce rate.
    • 💰 Sales breakdown — total sales split into free-cost marketing (organic, direct, referral, WhatsApp, SEO) and paid ads, plus a conversion-events table showing paid versus free per event.
    • Breakdowns — traffic sources, devices, campaigns and landing pages.
    • 👀 Visitor behaviour — scroll-depth and time-on-page distributions, and 🚪 exit pages showing where people leave.
    • Meta Pixel events — what was sent server-side.
    • Raw data — individual conversion events and visitor sessions, with source, medium, campaign, click ID and event ID.

  8. Act on what you see

    Three readings that reliably lead to a decision:

    1. Average scroll below 50% — your page is too long or the opening is not holding people. Move the offer up.
    2. High sessions, low conversion, from one source — that source is sending the wrong people. Change the targeting or the message.
    3. A specific exit page dominating — something on that page is losing the sale. Read it as a stranger would.

Tips

Common mistakes

Related

Keep reading

Browse all 11 tutorials, or read the blog for strategy and background.