One tracking platform.
Ten ad networks.

Meta: Available

Connection: Pixel ID and CAPI access token.

Matching signals: Available hashed email/phone, external ID, IP/user agent, fbp and fbc.

Event limits: Common funnel events plus eligible search, lead and registration events. Paired browser/server event IDs support deduplication; independent senders require review.

Setup and validation for Meta

Google: Available

Connection: For Google Ads, connect with Google, then pick up to 10 Google Ads accounts per store; WeProfit creates its conversion actions in each. For Google Analytics 4, sign in with Google and choose a property and web data stream, or enter the Measurement ID and Measurement Protocol API secret.

Matching signals: For Google Ads, the ad click ID (gclid, gbraid or wbraid) and the buyer’s hashed email or phone; matching by email or phone needs enhanced conversions turned on and the customer data terms accepted in Google Ads. For Google Analytics 4, available client and session IDs from the visitor’s Google Analytics cookies, and click context.

Event limits: Google Ads receives purchases from orders placed after the connection, uploaded about 6 hours after the ad click at the earliest. On Shopify stores, secondary actions also report new customer purchases, returning customer purchases and collection page views. WeProfit also loads the Google Ads tag of your connected accounts on your store, which sends page and product views for remarketing. When WeProfit adds the Google Analytics 4 tag, the browser sends page views and product views and the server sends the other events; when you keep your own tag, the server adds only purchases, refunds, leads, sign-ups and custom events. Importing Google Analytics 4 key events into Google Ads is optional.

Setup and validation for Google

TikTok: Available

Connection: Pixel ID and Events API token.

Matching signals: Available hashed email/phone, external ID, ttclid, ttp and IP/user agent.

Event limits: Common funnel events including page, content, cart and checkout; mappings depend on the eligible source event.

Pinterest: Available

Connection: Ad account ID and conversion token.

Matching signals: Requires hashed email or both IP and user agent. Includes epik when available.

Event limits: Common funnel events. Events without sufficient supported identity data are not eligible for delivery.

Snapchat: Available

Connection: Snap Pixel ID and Conversions API token.

Matching signals: Requires hashed email, hashed phone, or IP plus user agent.

Event limits: No lead event. Purchase requires value and currency; supported funnel mappings depend on the source event.

X Ads: Available

Connection: Pixel ID, Ads API OAuth credentials and per-event tags.

Matching signals: Requires twclid, hashed email or hashed phone. IP and user agent alone are insufficient.

Event limits: Each event needs its configured event tag. No lead event.

Microsoft: Pilot; enablement required

Connection: UET Tag ID and CAPI token.

Matching signals: Available Microsoft click and supported identity signals.

Event limits: Confirm Microsoft-side pilot access. Review existing UET tracking and use a dedicated tag where required to avoid mismatched deduplication.

Reddit: Available

Connection: Pixel/ad account ID and conversion token.

Matching signals: At least one supported identity signal is required, such as a click ID or supported user identifier.

Event limits: Standard events plus custom mappings for checkout and payment events; verify event mapping in destination diagnostics.

LinkedIn: Available

Connection: Ad account ID, CAPI token and conversion rule IDs.

Matching signals: A supported identity signal is required for the configured rule.

Event limits: Each event needs a conversion rule. Associate those rules with campaigns in LinkedIn.

Taboola: Click-attributed delivery

Connection: Account ID and matching conversion event names.

Matching signals: Requires the captured tblci Taboola click identifier.

Event limits: Only eligible Taboola-click-attributed events are sent. Page views are not forwarded; configured event names must match the destination.