Integrations

influence360 wallet attribution
ref:<REF_ID>
wallet:<CONNECTED_WALLET_ADDRESS>
chain:ETHEREUM
issuedAt:1700000000000

// A signed binding proves the visitor controls the wallet. Required when your attribution
// strictness is "Require signed"; it also wins over an unsigned binding under "Prefer signed".
async function onWalletConnected(address) {
  const signedAtMs = Date.now();

  // 1. Ask the pixel for the exact message to sign — never hand-roll it, a single character of
  //    difference and the signature will not verify (the binding is kept, but unsigned).
  const message = influence360.bindingMessage(address, 'ETHEREUM', signedAtMs);
  if (!message) return; // no referral captured — nothing to bind

  // 2. Sign it with the wallet client you already have. EVM shown; on Solana sign the same UTF-8
  //    bytes with ed25519 and hex-encode the 64-byte signature.
  const signature = await window.ethereum.request({
    method: 'personal_sign',
    params: [message, address],
  });

  // 3. Send the binding with the proof attached. Pass the SAME signedAtMs you signed with.
  influence360('identify', address, { chain: 'ETHEREUM', signature, signedAtMs });
}

I'm integrating Influence360 CPA web3 conversion tracking into my dApp. 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.
- On-chain conversions are DETECTED by Influence360 watching the contract configured on the campaign action — I never report them:
   - WALLET_ACTIVITY — a wallet interacted with the configured contract
   - TOKEN_ACQUISITION — a wallet acquired at least the configured minimum of the token
   - DEPOSIT_STAKE — a wallet deposited/staked at least the configured minimum
   - NFT_MINT — a wallet minted from the configured NFT collection
- What I DO have to integrate: binding the wallet the visitor connects to the referral they arrived with. Without that binding an on-chain action from that wallet has nothing to attribute to and the creator is never credited. This is the whole web3 integration.

SETUP — load the pixel (influence360.js) once on every page; it captures and persists the ref id:
   <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' });
   </script>

BIND — call this as soon as a wallet is connected, and again whenever the account changes:
   influence360('identify', '<connected-wallet-address>', { chain: '<CHAIN>' });

   Wire it into whatever my wallet library exposes (wagmi useAccount / RainbowKit / Reown-WalletConnect
   session, ethers provider 'accountsChanged', Solana wallet-adapter onConnect, …). It is fire-and-forget
   and never throws into the page. It is a no-op if no ref id was captured, so it is safe to call always.

SIGNED BINDINGS (recommended; required if my Influence360 attribution strictness is "Require signed")
- A plain identify call produces an UNSIGNED binding. A signed one proves the visitor controls the wallet:
  it wins over an unsigned binding for the same wallet under "Prefer signed" (the default), and is the ONLY
  kind that counts under "Require signed". Add the signature to the same call:
     const signedAtMs = Date.now();
     const message = influence360.bindingMessage(address, '<CHAIN>', signedAtMs);  // '' when no referral
     const signature = await window.ethereum.request({ method: 'personal_sign', params: [message, address] });
     influence360('identify', address, { chain: '<CHAIN>', signature, signedAtMs });
- Always build the message with influence360.bindingMessage(...) — do NOT hand-roll it. It must match the
  server's reconstruction byte-for-byte or the signature silently fails to verify and the binding lands
  unsigned. Pass the SAME signedAtMs to bindingMessage and to identify; it is signed into the message.
- EVM: personal_sign (EIP-191), 65-byte signature as hex.
  Solana: sign the same UTF-8 message bytes with ed25519 and hex-encode the 64-byte signature.
- signedAtMs must be within ~10 minutes of server time or the signature is treated as stale.
- Building the request myself instead of using the pixel? POST the same body to
  https://tracking.influence360.io/public/pixel/identify?publicToken=<YOUR_PUBLIC_TOKEN> as
  { "refId": "<ref id>", "wallet": "<address>", "chain": "<CHAIN>", "signature": "<hex>", "signedAtMs": <epoch ms> }

NOTES
- The ref id comes from the _influence360_ref_id first-party cookie the pixel writes; read it from there if I build the request myself.
- Signature verification supports: ETHEREUM, POLYGON, ARBITRUM, BASE, BSC, AVALANCHE, OPTIMISM, MANTLE, SOLANA. TRON bindings are accepted but can only ever be UNSIGNED, so they don't work under "Require signed".
- The public token is not a secret (it ships in the page), but bindings are only accepted from the domains allow-listed on that token — add my dApp's domain there.
- Add "test": true (or { test: true } on the pixel call) to fire a canary binding while wiring this up — validated the same way, never used to credit a payout.
- Re-binding the same wallet to the same referral is harmless; it is deduplicated.