Skip to main content
Converge is an ecommerce attribution platform: it follows the customer journey across your ad channels and reports spend, revenue, and ROAS by channel and campaign. Replo works with Converge in two independent ways; set up one or both.

​
Let Replo read your Converge data

Connect Converge in the Integrations app and Replo can query your attribution data directly in chat. You never leave the conversation to pull a report. Once connected, ask Replo for:
  • Performance by channel or campaign. Revenue, orders, sessions, ad spend, ROAS, CPA, clicks, and impressions over any date range, broken down by channel group, channel, campaign, ad set, or ad, using Converge’s attribution models.
  • Cohorts. Lifetime value or retention for customers acquired in a given period.
  • Your saved reports. The data behind an insight, dashboard, or analytics view you already built in Converge. Name the report and Replo pulls it.
  • What Converge tracks. The events, store dimensions, and channel or campaign names in your workspace, so a question like “how is my Summer Sale campaign doing” lands on the right campaign.
Point Replo at the integration with an @-mention so there is no doubt which tool you mean.
Custom queries come back with a link to the same query in Converge, so you can open it there and keep exploring.

​
Connect Converge

Converge connects with a personal API key; there is no sign-in flow. Like other analytics tools, the Converge card offers a Project connection (shared with everyone on the project) and a Personal one (only for you). Connect either or both.
1

Create an API key in Converge

In Converge, open your account settings and go to API keys. Create a key and copy it right away: it starts with cvg_ and Converge only shows it once.
2

Open the Integrations app

In Replo, open the Integrations app and find Converge.
3

Paste the key and connect

In the Project or Personal block, paste the key and click Connect. If your Converge account can reach more than one workspace, Replo lists them and asks for the Workspace ID to use.
You can also connect straight from chat; if you ask Replo to use Converge before it’s connected, it drops the connection card into the conversation.
A Converge API key belongs to the person who created it, not to the workspace. If that person is removed from the Converge workspace, the key stops working and the Integrations app tags the connection Reconnect needed. Create the key from an account that stays on the workspace.

​
Track your site with the Converge pixel

The pixel is separate from the data connection: it runs on your published pages so Converge can attribute the traffic and orders that come through them. Ask Replo to add it and give it the public token of your client-side event source.
Replo installs the pixel as a managed script that loads through Replo’s consent layer, so it stays GDPR and CCPA compliant. Page views, product views, add to cart, checkout, and purchase events fire automatically. Tracking starts on every page once you publish. See Adding Scripts for more on site-wide pixels.

​
Finding your public token

  1. In Converge, go to Data management and open Event sources.
  2. Select your client-side source and open the HTML install option.
  3. The token is the part of the script URL before .js (for example, abc123 in https://static.runconverge.com/pixels/abc123.js).
Server-side event sources have a webhook token instead. It is a secret credential and does not work as a pixel; pasting it into your site would publish it. If Replo asks for a different token, use the client-side source’s public token.
The two setups are independent. The pixel feeds events into Converge; the API key lets Replo read attribution back out. Most merchants do both.