Events CSV Upload

What this integration does

The Events CSV Upload takes a CSV file and sends each row into Attribution as if your site or server had tracked it: a track row becomes an event, an identify row attaches traits to a person, a page row becomes a visit. Use it for conversions that live in a system without an integration, for historical data, or for a one-off correction.

Open it from Integrations → Conversion Integrations → Events CSV Upload, or Settings → Events uploader. The uploader validates the file first and reports what it would create before processing it, and offers a header generator for each row type.

File format

• A .csv file; comma, semicolon, tab and pipe delimiters are detected.
• A type column, the same for every row of the file: track, identify or page.
• Columns allowed: anonymous_id, user_id, event, message_id, timestamp, type, and nested fields written with a dot: properties.revenue, traits.email, context.atb_track_by_email. Any other header is rejected.
• Every row names the person: user_id, anonymous_id, or context.atb_track_by_email with the email to match on.
• track rows need event, message_id and an ISO 8601 timestamp; page rows need message_id, timestamp and properties.url; identify rows need neither timestamp nor message id.
• Revenue goes in properties.revenue, in major units.

Limits

• 5,000 rows per file. Split larger files, or use the Tracking API for ongoing volume.
• Rows arrive through the normal pipeline, so they appear on the dashboard after the next data refresh.