// First-party Data & Attribution
Every ticket sale builds a first-party fan record you own outright. Push those purchases server-side to Meta and Google so your attribution survives ad-blockers and privacy changes, then activate the audience in the CRM you already run.
// Why it matters
Fan record
One first-party record per fan across tickets, memberships and spend
Attribution
Server-side purchase events that survive ad-blockers and cookie loss
Activation
Sync audiences straight into HubSpot, Salesforce and your ad platforms
Ownership
100% yours. Legally siloed, never pooled with other organisations
01
On a marketplace, the buyer belongs to the platform and you rent access to your own audience. On INTIX, every fan becomes a first-party record on your account, complete with orders, membership status, attendance and spend. Yours to keep, export and market to.
{
"fan_id": "fan_9Qe2",
"email": "supporter@example.com",
"lifetime_value": 1840,
"membership": "season-2026",
"events_attended": 14,
"channel": "web",
"consent": { "marketing": true }
}02
Browser pixels are being blocked by ad-blockers, Safari ITP and privacy updates, so a growing share of your sales never gets attributed. Forward INTIX purchase events server-side to the Meta Conversions API and Google, and recover the conversions the pixel misses. Cleaner ROAS, real numbers.
// Forward every purchase to Meta's Conversions API, server-side
app.post("/intix/webhook", async (req, res) => {
const { fan, order } = req.body.data;
await fetch(`https://graph.facebook.com/v19.0/${PIXEL_ID}/events`, {
method: "POST",
body: JSON.stringify({
data: [{
event_name: "Purchase",
action_source: "website",
user_data: hash({ em: fan.email, ph: fan.phone }),
custom_data: { currency: "NZD", value: order.total / 100 }
}],
access_token: META_CAPI_TOKEN
})
});
res.sendStatus(200);
});03
First-party data is only worth having if you can act on it. INTIX sync keeps purchase history, membership status and segments flowing into HubSpot, Salesforce and your ad platforms, so lifecycle marketing, lookalikes and abandoned-cart recovery run on live data.
// Keep the CRM current on every membership change
if (evt.type === "member.updated") {
crm.upsertContact({
email: evt.data.fan.email,
lifecycle: evt.data.membership.status,
segment: evt.data.fan.lifetime_value > 1000
? "high-value"
: "standard"
});
}Your first-party data does not stay trapped in the ticketing tool. Push it to the CRM, analytics and ad platforms your team lives in.








Where your fan data lives, and whether your attribution survives modern privacy defaults, depends on the model you run.
| INTIX (first-party) | Marketplace | Pixel-only | |
|---|---|---|---|
| Who owns the fan record | You do, 100% | Platform-owned | You, but thin |
| Data completeness | Full purchase + member record | Restricted export | Whatever the pixel caught |
| Survives ad-blockers / ITP | Yes, server-side | Vendor-controlled | Degrades badly |
| Meta / Google Conversions API | Fed from server-side events | Not available | Client-side only |
| CRM activation | Native + API | Manual export | Not supported |
| Audience portability | Yours to take anywhere | Locked in | Siloed per platform |
First-party data
See how INTIX turns every ticket sale into first-party data you own and attribution you can trust.