Send results to your ad accounts

Ad platforms bid better when they know which clicks became customers. Datacenter sends your leads and sales to each ad account you turn on, from our server, so blockers and short cookie lives do not hide them. It is on paid plans: Solo, Studio, Agency and Custom. Meta has its own card: see Meta Conversions API.

Turn a platform on#

Open your site's Settings, then Integrations, and find Send results to your ad accounts. Each platform is one row.

• TikTok, Pinterest, Snapchat and Reddit: click Connect, paste the id and the access token from the platform's events manager (the page says where), then Save and turn on.
• Google Ads, Microsoft Ads and LinkedIn (when shipped): connect the platform under Ad spend first, then click Turn on. Datacenter makes its own conversion actions in your account: "Datacenter lead", "Datacenter sale" and, for Google, "Datacenter closed deal".

Pick what to send#

Under What to send, tick the goals. A goal named like a purchase goes as a sale, with its value; the rest go as leads. When one visit reaches two ticked goals, it goes once, as the sale.

Deals you win in your CRM sends HubSpot and GoHighLevel deals marked won to Google Ads and Microsoft Ads, with the deal value, so bidding learns from closed business, not only form fills. Turn it off there if you would rather not.

Live Stripe and Shopify sales on a ticked Purchase goal go too.

Refunds#

When a sale you sent is refunded, in full or in part, from Stripe, Shopify or the Events API, Datacenter tells each platform that has a way to hear it, so its revenue and return on ad spend stay true. Refunds under What to send is on by default.

A refund is sent once, even when Stripe tells Datacenter twice. Refunds go out for sales sent in the last 30 days, in the sale's own currency. The Delivery log lists each one beside its sale. A visitor who sent Global Privacy Control is never sent, refund or not.

Google Ads conversions go through Google's Data Manager API. When Google Ads is switched on for Datacenter, sites that connected Google before need to Reconnect under Ad spend once, to allow it.

How each conversion is matched#

Click ids last 90 days with 90-day tracking, so a sale or won deal days after the click still names it. Emails and phones come from the Events API, your store or your CRM, and leave Datacenter hashed with SHA-256. If nothing can be matched, nothing is sent.

On a site that waits for consent, nothing goes until the visitor agreed.

Global Privacy Control#

When a visitor's browser sends Global Privacy Control (the Sec-GPC: 1 header), Datacenter sends nothing about that visit to any ad platform: not to Meta, not to the platforms on this card. California treats the signal as a request to opt out of the sale and sharing of personal data, and sending conversions to ad platforms is sharing. With 90-day tracking, the signal is also kept with the visitor's random id for 13 months, so a later sale, won deal or Events API call tied to that id is not sent either, and ad click ids are not kept for them.

Your own statistics still count the visit. The Delivery log says how many conversions were held back this way in the last 30 days. There is nothing to set up.

Check it#

The row shows when it last sent and how many sends carried a click or contact details. Delivery log lists the last 100 sends with each platform's answer. Failed sends retry with growing gaps for 24 hours. If a platform refuses your token or login, the row says Needs attention and sends wait until you fix it.