Prepare customer-safe CSVs

Use this when CS needs to share campaign-event evidence with a customer.

Allowed columns

Prefer:

• Recipient email.
• Recipient name, if already customer-visible.
• Campaign name.
• Event type.
• Event timestamp.
• Classification: likely human, likely scanner, or inconclusive.
• Short support note.

Do not include

• API tokens.
• Internal IDs unless already customer-visible.
• Raw IP addresses unless approved for the customer response.
• Cross-tenant data.
• ActiveAdmin URLs.
• Internal comments.

Steps

1. Export or copy only the rows needed for the customer question.
2. Remove unrelated recipients.
3. Remove internal-only fields.
4. Add a clear classification column if scanner behavior is being discussed.
5. Sanity-check that every row belongs to the correct customer and campaign.
6. Attach the CSV to the ticket or customer email only after review.

Escalate when

• The customer requests raw event data not visible in ActiveAdmin.
• You are unsure whether a field is safe to share.
• The CSV will be used for legal, contractual, or executive reporting.