Appearance
Integration combinations
Every connector in the catalogue lands in the same shared data model. Events, content, daily metrics and identity edges look the same whether they came from a shop, an email platform, a marketplace or your own tracker.
That is what makes the combinations work. Nobody has to write a join between two vendor schemas, because there is only one schema.
The pieces
| Piece | What it holds |
|---|---|
| Events | Something happened, when, to whom, worth how much |
| Content | Every URL, product and asset any source has ever seen |
| Daily metrics | Pre-aggregated numbers that must stay as the platform defined them |
| Identity edges | Two identifiers that belong to the same person, contributed by a source |
| Identity map | The resolved person, built from every edge every source contributed |
Revenue and marketing
Shopify plus Klaviyo: what the campaign was worth
Email platforms report opens and clicks because that is what they can see. Joined on the identity graph, every campaign and flow gets a revenue figure, net of the refunds the email platform never hears about.
What it answers: which flow earns its place, which segment is large and inert, whether the discount code in the subject line cost more than it brought.
Google Ads plus Shopify: return on ad spend you can defend
The ad platform reports its own conversions using its own attribution model. The click id lands on the ad side and on the order side, so the join is deterministic rather than modelled, and refunds are subtracted because the shop knows about them.
What it answers: what each campaign actually banked, per day, after returns.
→ Google Ads + Shopify
Bol.com plus Shopify: which channel is actually worth it
Marketplace revenue looks larger than own-shop revenue until commission and returns are subtracted. Both land here, per order item, and the twin order is matched on the id both systems carry.
What it answers: margin per product per channel, and whether the marketplace is a growth channel or a volume habit.
Measurement and search
First-party tracker plus GA4: how much traffic your analytics is hiding
Third-party analytics is consent-gated and blockable. A first-party tracker is neither. Run both and the difference between them becomes a number.
What it answers: what share of your real traffic your reporting has been missing, per day and per page.
Search Console plus the tracker: what the searcher did next
Search Console stops at the click. The tracker starts there. Same URL, same day, joined.
What it answers: which queries bring people who read, and which bring people who bounce. High impressions with a bad on-site outcome is a content problem, not a ranking problem.
→ Search Console + first-party tracker
Search Console plus Google Ads: stop paying for what you own
Terms where you rank well organically and still buy the click.
What it answers: the fastest budget saving available in most accounts.
Content that knows things
Search Console plus the content pipeline: briefs from proven demand
Queries that already earn impressions on your domain are the cheapest articles you will ever write, because the demand is measured before a word is drafted.
What it answers: what to write next, ranked by evidence rather than by opinion.
Your documents plus everything: the company brain
Index Google Drive or upload your own material, and the same grounded knowledge is available to the chat widget, the content pipeline, the playbooks and your team's AI assistants over MCP.
What it answers: questions about your business, in your terminology, with a reference back to the document the answer came from, so the answer can be checked rather than taken on trust.
Company brain plus Shopify plus Odoo: answers with facts underneath
Documents explain the policy. The shop knows the order. The ERP knows the project. An assistant with all three answers a customer question completely instead of partially.
→ Google Drive + Shopify + Odoo
Publishing loops
One article, every channel
An approved article becomes a native post per channel, each written for that channel rather than truncated into it, all from one approval.
→ Articles + LinkedIn, Instagram, Facebook, Threads, Bluesky, Pinterest, Telegram, TikTok
Publish, then measure, then brief the next one
Posts carry campaign parameters. The tracker reads them back. The shop attributes revenue. Search Console shows what the article started ranking for. That evidence becomes the brief for the next article.
What it answers: whether the content programme is working, with the loop closed rather than assumed.
Business workflows
Intake form plus Odoo plus approval
A website enquiry becomes a draft quotation with real line items, waiting for a human to confirm.
→ Intake forms + Odoo + Slack
Sheet plus playbook plus write-back
A column of messy input goes in, a column of clean structured output comes back, and nobody pasted a prompt three hundred times.
Do not see your combination?
The pieces are generic on purpose. If two of your systems can both be connected, they can be joined. Webhooks and the API cover the rest, and we take requests.