Send every Loop Subscriptions event to MGID, server-side

Loop SubscriptionsWhat it sends

• subscription_idthe Loop subscription across its whole life
• email / phonesubscriber contact
• event_typerenewal, swap, skip, pause, cancel or save
• line_itemsproducts after any swap
• total / intervalcharge amount and billing cadence

Resolved before it is sent

• IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
• customer_typeNew or returning, resolved before send.
• DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
• Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

MGIDWhat it receives

• hashed email / phoneidentity matching on arrival
• mgid_click_idcredit the click that drove it
• external_idstable person across sessions
• event_iddedupe against the browser pixel
• value / currencyvalue-based bidding