We offer custom reporting exports that are tailor-made for specific customers.
The reports are available in CSV, JSON, and XLSX format.
They can be downloaded in our interface or integrated into a customer’s infrastructure using a static URL from which the report can be downloaded.
When you buy a custom export/report, you can find these when you go to Reports
> Custom exports
.
Here, you can choose the desired format and generate your export.
What information do you need to provide when requesting a custom export?
You can look at a custom export like a single tab from an Excel sheet. It has rows and columns.
Rows
First off, you'll need to decide what makes for a row.
What makes a row will usually (though this isn't a requirement) include a time component. Examples: a row for every day, week, or month.
It could also include other components, some examples: a row per campaign, message, or member, a row per campaign tag, or a combination of all these things.
An elaborate example would be: Every unique combination of "day," "share network," and "member" should be the components that group data into a row.
Less common, but also possible, are exports with a single row. In this case, calculations from the columns (below) are aggregated over all the data from the export into a single row.
Columns
Next up, we have the columns. All the components that make up a row will automatically get their own column. In the previous example, you'd get three columns (day, share network, and member.)
Additionally, you can define extra columns that have reporting data for those rows. What's in these columns is up to you. Some examples are listed below to give you an idea.
The total amount of interactions
The number of clicks generated
A comma-separated list of all member groups from all the members that shared
The number of campaigns that were published
...
This is basically where you define what your business needs and what is important for you to know.
Your export's time range
Custom exports have a predetermined time range. The time range is always relative to the moment the export is being downloaded. For example, if the time range is "last seven days," every time the custom export is downloaded, it will contain data from the seven days prior to the moment when the export is downloaded.
Full example
Taking our rows from the example above and assuming what we want to know is the total amount of shares and clicks generated over the last three days, such an export would look like this:
Date | Share Network | Member | Shares | Clicks |
2023-11-28 | John | 12 | 110 | |
2023-11-28 | Lara | 8 | 10 | |
2023-11-28 | John | 1 | 98 | |
2023-11-28 | Lara | 4 | 210 | |
2023-11-27 | John | 12 | 110 | |
2023-11-27 | Lara | 8 | 10 | |
2023-11-27 | John | 1 | 98 | |
2023-11-27 | Lara | 4 | 210 | |
2023-11-26 | John | 12 | 110 | |
2023-11-26 | Lara | 8 | 10 | |
2023-11-26 | John | 1 | 98 | |
2023-11-26 | Lara | 4 | 210 |
Additional information for IT teams:
If you programmatically need access to custom reports, you can get the report URL on this page. This can be useful to integrate (ingest) the data from Ambassify in your Business intelligence tools (BI software).
Exports are protected using an authentication token. When requesting the export URL, this token should be set in the Authorization header preceded by the keyword Bearer and a space. For example, Authorization: Bearer this-is-my-token. Tokens can be acquired on the API Tokens settings page (settings
> technical
> API tokens
).
Here, you can create a new token. Give your token a clear description to know this is the token you created for the custom exports. Save the token securely if you need it more than once.
Tokens don't expire, but if you ever need to expire a token for security reasons, you can do this on this page.