Advertising Channel with Scheduled CSVs through Mail

Mail CSV is the lowest-friction way to bring data into Clarisights when your advertising platform or vendor already emails CSV reports on a schedule. You email the report to a unique inbound address we provision for you, and Clarisights ingests the attached CSVs on the configured cadence.

At a glance

Authentication options

Mail CSV uses an email address as the auth boundary. Clarisights provisions a unique inbound email address for your connection — anything sent to that address is ingested into your workspace, and nothing else can reach it. There are no API keys, OAuth flows, or passwords to manage.

• Keep the inbound email address private. Treat it like a credential and only share it with the person or system that should be sending reports.

• If the address is ever exposed or needs to change, your CSM can rotate it.

Setting up the connection

Step 1 — Request a Mail CSV connection

Reach out to your CSM and let them know you want to set up a Mail CSV pipeline. Confirm which platform or vendor will be sending the reports and how often.

Step 2 — Receive your unique inbound email address

Clarisights provisions a unique email address for this pipeline and shares it with you. Every CSV emailed to this address will land in this connection only.

Step 3 — Configure the report to be emailed to that address

In your advertising platform's reporting UI (or in your vendor's scheduler), set up a recurring CSV export and add the Clarisights inbound address as the recipient.

⚠ Common error: Attachment not received → the report is going to the wrong address. Double-check the recipient against the address Clarisights provided — including any plus-tags or subdomain.

Step 4 — (Optional) Share the ZIP password

If your vendor sends CSVs inside a password-protected ZIP, share the unzip password with your CSM ahead of time so we can decrypt incoming attachments.

⚠ Common error: Decrypt failed → the ZIP password on file doesn't match the one used to encrypt the attachment. Confirm the current password with your vendor and resend it to your CSM.

Step 5 — Pipeline ingests on the configured cadence

Once emails start arriving, the pipeline picks them up on its configured schedule and processes the attached CSVs. New rows appear in the channel's reports after the next ingestion run.

⚠ Common error: Schema mismatch → the CSV's header row doesn't match the columns the pipeline expects. Make sure the report layout in your vendor's UI hasn't changed and that no extra columns were added or removed.

Connection details exchange

What we read

• Attachments only. Clarisights reads only CSV files attached to the email. The subject line and email body are ignored, so it's safe for the sender to include any commentary or formatting in the message.

• First row as header. The first row of every CSV is treated as the column header. Data rows start from row two.

• ZIP attachments. Password-protected ZIPs are unzipped on receipt using the password you've shared with your CSM, and the CSVs inside are processed as if they had been attached directly.

Connector specifics

• Attachment size. Standard email attachment limits apply — roughly 25 MB per email across all attachments. If your reports are consistently larger than this, an SFTP, S3, or warehouse connector is a better fit.

• Password-protected ZIPs. Supported, but the unzip password must be shared with Clarisights ahead of time. If you rotate the password, let your CSM know before the next send.

• Multiple attachments per email. Each attachment is treated as its own file in the same logical dataset. The schema (column names and order) must match across all attachments in a single email.

Limitations & known constraints

• Per-email attachment cap of roughly 25 MB. For larger volumes, use SFTP, S3, or a warehouse connector instead.

• Inline CSVs (data pasted into the email body) are not supported — the report must be a file attachment.

• Only CSV is supported. HTML email reports, PDFs, and Excel files are not ingested.

Operating notes

• Refresh cadence is configured per pipeline. Coordinate with your CSM if the upstream send schedule changes.

• Rotating the inbound email address (for example, after exposure) requires a CSM action — reach out to support to issue a new address.

• If your vendor changes the report layout, the schema in Clarisights needs to be updated to match. Send a sample of the new CSV to your CSM before the upstream change goes live.

Need help?

When contacting support from the in-app messenger, please include:

• The integration name and account ID (Integrations → Channel)

• The exact error message or screenshot

• The step where the issue occurred

• When the issue started