Integrations

I'm integrating Influence360 CPA conversion tracking into my website using the browser pixel. Generate the code for my stack and explain where each piece goes.

CONTEXT
- An influencer link sends a visitor to my site with an Influence360 ref id in the destination URL. The pixel below captures and persists it automatically (first-party cookie), so I only report the conversion event.

SETUP — load the pixel (influence360.js) once on every page:
   <script>
     !(function(w,d){w.influence360=w.influence360||function(){(w.influence360.q=w.influence360.q||[]).push(arguments)};var s=d.createElement('script');s.async=1;s.src='https://tracking-pixel.influence360.io/v1/influence360.js';d.head.appendChild(s)})(window,document);
     influence360('init', '<YOUR_PUBLIC_TOKEN>', { collectUrl: 'https://tracking.influence360.io/public/pixel/conversion' });  // every page — captures the ref id
   </script>

REPORT — on each conversion success page, call (use the matching event type):
   - SIGN_UP — a new user registered
     influence360('track', 'SIGN_UP', { dedupKey: '<your-order-or-user-id>' });
   - KYC_VERIFICATION — a user passed identity verification
     influence360('track', 'KYC_VERIFICATION', { dedupKey: '<your-order-or-user-id>' });
   - APP_INSTALL — a user installed the app
     influence360('track', 'APP_INSTALL', { dedupKey: '<your-order-or-user-id>' });
   - PURCHASE (orderValue required) — a paid order (orderValue = order amount)
     influence360('track', 'PURCHASE', { dedupKey: '<your-order-or-user-id>', orderValue: '49.99' });
   - DEPOSIT (depositValue required) — a funded deposit (depositValue = deposit amount)
     influence360('track', 'DEPOSIT', { dedupKey: '<your-order-or-user-id>', depositValue: '49.99' });
   - SUBSCRIPTION (qualifyingPlan required) — a paid subscription (qualifyingPlan = the plan the user subscribed to; payout is plan-driven)
     influence360('track', 'SUBSCRIPTION', { dedupKey: '<your-order-or-user-id>', qualifyingPlan: 'pro-monthly' });

NOTES
- influence360('init', ...) must run on every page so the ref id is captured site-wide.
- To route events through your own proxy or a regional/staging collector, change collectUrl.
- dedupKey (a stable order/user id) makes retries idempotent — always send it. Omitting it on the pixel disables duplicate protection entirely, so a double-submitted checkout counts twice.
- Monetary events must send their type-specific amount field (PURCHASE → orderValue, DEPOSIT → depositValue); it has to meet the action's configured minimum or the conversion is rejected.
- PREFER THE SERVER POSTBACK FOR PURCHASE AND DEPOSIT if my backend can report them: an amount reported from the browser is whatever the page sends (a visitor can edit it), the pixel cannot reverse a conversion after a refund or chargeback, and the pixel endpoint always answers 204 so a rejected event is indistinguishable from an accepted one. Use the pixel for the events that carry no amount (SIGN_UP, KYC_VERIFICATION, APP_INSTALL, SUBSCRIPTION). If you wire a purchase or deposit through the pixel anyway, tell me why and flag it in your summary.
- SUBSCRIPTION must send qualifyingPlan (the plan the user subscribed to); its payout is decided by matching that plan against the action's configured plan tiers — an unlisted plan is rejected — so it carries no amount.
- Web3 events (WALLET_ACTIVITY, TOKEN_ACQUISITION, DEPOSIT_STAKE, NFT_MINT) are DETECTED on-chain — you never report them — but they still need the visitor's wallet tied to the referral, which does take client code: call influence360('identify', '<connected-wallet-address>', { chain: 'ETHEREUM' }) right after the wallet connects. Without that binding (or an on-chain referral tag) an on-chain conversion has nothing to attribute and is never credited.