Connects to the stack you already run
Live through an API or as a spreadsheet export -- and several of these are publishing destinations too. This is also the layer that replaces a standalone CDP: every source below feeds the same identity-resolved data set, not nine separate exports.
Salesforce
Loyalty tier, purchase history, and lifecycle stage feed identity resolution.
Shopify & commerce platforms
Order value, SKU-level detail, returns, and promo use.
Klaviyo
Opens, clicks, flows, and revenue per send -- and where approved emails ship as drafts.
Google Ads
Search term and conversion data in; RSA drafts created under review, out.
Google Search Console
Query, landing page, position, and click-through rate.
Meta Ads
Engagement data in; paid social drafts out to Meta Ads Manager.
TikTok Shop
Product saves and cart events feed identity-level profiles.
Amazon Seller Central
A+ content and product pages submitted for Amazon review.
The Trade Desk
Audience segment data in; display creative uploaded and paused, out.
One identity layer
Every source resolves to the same customer record.
Drafts, not live pushes
Outbound connectors stage content for your review.
Live or flat-file
Connect an API, or start with a CSV export -- your call.
Why this list matters more than it looks
Any one of these connections is easy to build. What's hard -- and what most marketing stacks never actually achieve -- is having all of them write into the same identity-resolved profile, so a purchase in Shopify, an open in Klaviyo, and a search term in Google Ads all attach to the same customer record instead of living in three disconnected systems that each only know a third of the story.
Inputs build the personas. Outputs publish the content.
Triangul8 connects in two distinct directions. Inputs teach the engine who your customers actually are - that's what persona development runs on. Outputs receive the finished, persona-targeted content as drafts. Several platforms do both, because their performance data is as useful going in as your content is coming out.
Inputs
Data that builds your personasSalesforceCRM profiles, lifecycle, LTVWeb analytics (GA4)On-site behavior & journeysGoogle Search ConsoleQueries, impressions, rankingsShopifyOrders, products, value, frequencyBothKlaviyoEmail engagement & lifecycleBothGoogle AdsSpend, conversions, audiencesBothMeta AdsCampaign & audience performanceBothTikTok ShopSocial commerce performanceBothAmazon Seller CentralMarketplace sales dataBothOutputs
Where approved content publishesThe Trade DeskProgrammatic display creativeKlaviyoCampaigns & lifecycle flowsBothGoogle AdsSearch & shopping ad copyBothShopifyProduct & collection contentBothMeta AdsPaid social copy & briefsBothTikTok ShopProduct & creative contentBothAmazon Seller CentralA+ content & detail pagesBothLive sync or flat-file - your call
Connect or upload
Authenticate a live connector for automatic, ongoing sync - or start with a flat-file / CSV export if you'd rather not connect systems on day one. Both feed the same data layer.
Map & resolve identity
Fields are mapped to what the engine understands, and records for the same person across systems are stitched into one profile - the step a stack of point tools never does.
Publish back as drafts
Approved content is pushed into the same platforms as drafts or paused items, so nothing goes live without a person's explicit sign-off.
Common integration questions
Do I have to connect live systems to get started?
No. You can begin with a flat-file or CSV export of your customer and order data and add live connectors later. Live sync simply keeps personas refreshing automatically instead of on manual upload.
Does Triangul8 replace my CDP?
For most teams, yes. The identity-resolution layer that unifies your sources into one profile per customer is the core job of a CDP - and it's built into Triangul8, feeding persona development directly instead of exporting to yet another tool.
Will content publish to my tools automatically?
Only as drafts. Outbound connectors push approved content into your CMS, ESP, ad platforms, and marketplace tools as drafts or paused items. A human always makes the final call to go live.
What if my platform isn't listed?
The listed connectors are the most common, but the data layer accepts flat-file and API sources broadly. If you don't see your stack, tell us what you run and we'll confirm the path in a quick call.
Is my data shared across other Triangul8 customers?
No. Your first-party data, the resolved profiles, and the personas built from them are used for your account only - never pooled or shared.
See what your existing tools already know
Your CRM, commerce platform, and ad accounts each hold a fragment of the customer. We'll show you what happens when they're resolved into one profile - and how approved content flows back out to the same tools.
- We'll map your specific stack
- See identity resolution in practice
- Flat-file works if you're not ready to connect