Snapchat Ads and Telegram: the Conversions API v3 up to the deposit

Each CRM event maps to a Snapchat event. Names can be changed per pixel, and each rule can be turned on or off.

The data sent with each event

• The Snapchat click ID (ScCid URL parameter) and the _scid cookie of the original click.
• The lead’s email and phone, hashed with SHA-256.
• The click’s IP address and browser, with the landing page address.
• A unique event ID.

At least the click ID, the cookie, an email or a phone is needed: without them, the event is not sent.

1. In the CRM’s Tracking screen, add your Snapchat pixel with its ID and a Conversions API access token.
2. Test the connection: ScaleGram uses Snapchat’s validation endpoint, which checks the event without counting it.
3. Create a tracking campaign and use its link in your Snapchat ad, with ad={{ad.id}}&adset={{adSquad.id}}&camp={{campaign.id}} to know which ad brought each lead.

The triggers are the same as for Meta Ads and TikTok Ads: the join when your bot sees the new member, the lead when a conversation becomes a lead, the registration at the pipeline stage you choose or through CellXpert, the deposit once confirmed. A failed send is retried after 1, 5, 30, 120 and then 720 minutes.

• Snapchat spend is not imported: the cost per depositor cannot be read in the CRM for these campaigns.
• There is no test event code as with Meta or TikTok: the test goes through the validation endpoint.
• A join through the channel’s public link has no original click: Snapchat cannot tie it to an ad.
• A deposit cancelled afterwards is not removed from Snapchat.