CSV upload
A CSV upload does what the API does, one row per action or offer, for teams without developers. Upload files in the dashboard, under Developers, then CSV upload. Each upload returns a result for every row: earned, or not and why, or what was wrong with the row.
Actions
Section titled “Actions”One row per action, with the same fields as POST /actions:
| Column | Required | What it holds |
|---|---|---|
reference |
Yes | Your own unique ID for the action. Uploading the same row twice never pays twice. |
campaign_id |
Yes | The campaign, such as cmp_01JA9TQ4W2D8M5X4N6B1C0VEKA. |
action |
Yes | The action’s key, as set in the campaign, such as weekly_deposit. |
customer_id |
Yes | Your own ID for the customer. Never names. |
phone_number |
Yes | The customer’s number, in E.164 format, such as +2348000000001. |
occurred_at |
Yes | When the customer did it, in ISO 8601 with a UTC offset, such as 2026-10-20T09:40:00+01:00. |
source |
No | Where the customer came from. |
friend_customer_id |
Referrals only | The friend’s customer ID. |
friend_phone_number |
Referrals only | The friend’s number, in E.164 format. |
amount_naira |
When the plan sets an amount | What the action carried, in naira, such as 10000 for ₦10,000. |
count |
When the plan sets a count | What the action carried, such as 52 transactions. |
reference,campaign_id,action,customer_id,phone_number,occurred_at,source,friend_customer_id,friend_phone_number,amount_naira,countdep-889431,cmp_01JA9TQ4W2D8M5X4N6B1C0VEKA,weekly_deposit,CUS-204871,+2348000000001,2026-10-20T09:40:00+01:00,app,,,10000,ref-120554,cmp_01JA9TQ4W2D8M5X4N6B1C0VEKA,friend_first_deposit,CUS-204871,+2348000000001,2026-10-20T10:05:00+01:00,,CUS-311902,+2348000000002,5000,Offers
Section titled “Offers”For campaigns that start plans by offer, one row per customer you are offering the plan to:
| Column | Required | What it holds |
|---|---|---|
reference |
Yes | Your own unique ID for the offer. |
campaign_id |
Yes | The campaign. |
customer_id |
Yes | Your own ID for the customer. |
phone_number |
Yes | The customer’s number, in E.164 format. |
source |
No | Where the offer went out, such as a campaign in your app. |
reference,campaign_id,customer_id,phone_number,sourceoff-552018,cmp_01JAE3M8Q4W7T2K9R5F1H6P3NB,CUS-204871,+2348000000001,october_offerResults
Section titled “Results”Every row gets the same answer the API would give, and the same rules apply:
- A row that earned data says so, and the data is delivered as for any action.
- A row that earned nothing gives its reason, and Aura sends
reward.rejectedfor it, unless the customer is in the comparison group. - A row that is wrong, such as a bad phone number or an unknown action, gives the error and records nothing.
- The
referencerule is the same as the API’s: a row already uploaded with the same values returns its original result, so uploading a file twice never pays twice.
© 2026 PressOne Africa Limited ·poweredbyaura.com ·Privacy ·Terms