This connector is for Audiense Insights (audience intelligence reports). Audiense Online (e-commerce conversion tracking powered by Elevar) is a different product and is not covered by this connector.
Before you start
The connector reads Audiense with API credentials (Client ID and Client Secret) created in your Audiense account. In Audiense Insights, they are under Settings > Project Settings > Connected Accounts.API access depends on your Audiense plan. If you cannot find the credentials, or the connection is refused, ask your Audiense account manager to enable API access for your account.
Configuring Audiense as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Audiense option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
The following configurations are available:- Client ID: The Client ID of your Audiense API credentials.
- Client Secret: The Client Secret shown next to it.
- Report IDs: (Advanced, optional) Read only these intelligence reports. The ID is in the address of the report when you open it in Audiense. Leave it empty to read every report of the account. A value that does not match a report the account can open makes the run fail with that value in the log.
- Maximum influencers per audience: (Advanced, optional) Keep only the top N influencers (by affinity) of each audience and segment. Leave it empty to load the whole ranking. When the limit cuts a ranking, the run log says so.
2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: every Audiense stream is FULL_TABLE. Each run reads the current list of reports and their analyses, so a new report, a report that finished generating, or a deleted report is reflected on the next run.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you create reports in Audiense. A daily run is usually enough. Each run reads every report again, including the influencer ranking of every audience, so accounts with many reports take longer; use Report IDs or Maximum influencers per audience to keep runs short. Optionally, you can define some additional settings:- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- An Additional Full Sync is not needed: every run is already a full read.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Available streams
The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.
Every analysis row carries
report_id and audience_id. audience_id is the segment ID, or full_audience for the whole audience of the report, so you can join the analyses with report_audiences and reports. Detailed or nested data (for example the content analysis, or the complete report as returned by Audiense) is stored as JSON text, for example json_extract_scalar(liked_content, '$.topHashtags[0].key').
Reports still being generated appear in
reports with their status, but their audiences and analyses are loaded only on a run after Audiense finishes them. Reports that failed in Audiense, or that return no audience, appear only in reports. The run log says how many reports are in each case. If no report is visible at all, the run log asks you to check that the credentials belong to the Audiense account that has the reports. When a report that is being regenerated still lists its audiences but Audiense has no analyses for them yet, that report is skipped in the analysis tables with a warning and loaded on a later run.Insights of the full audience and content analysis: Audiense provides them per audience only when the report includes them. When a report does not, those rows are not in the tables (
report_audiences shows which analyses each audience has), and the run log warns you. The Audience content stream is not selected by default: it will be enabled by default once it is validated on a first live run. You can still select it.Errors: if Audiense refuses one of the analyses (for example, your plan does not include influencers), that stream fails with the audience and Audiense’s message in the run log, and the other streams are still extracted. If a list cannot be read consistently, or Audiense returns an unexpected response, the stream fails instead of saving a partial table. If Audiense returns the report list or an influencer ranking without pagination information, the run log asks you to confirm that nothing is missing. A report deleted while the sync runs is skipped with a warning.
Fields by stream
Reports
Reports
Stream name:
reports. One row per intelligence report.Sync Strategy:- Full table (every run reads the current state)
- Primary key(s):
id
Report audiences
Report audiences
Stream name:
report_audiences. One row per audience of each finished report: its full audience and each segment.Sync Strategy:- Full table (every run reads the current state)
- Primary key(s):
report_id,audience_id
Audience insights
Audience insights
Stream name:
audience_insights. One row per value of each insight of each audience (for example, the share of women in a segment).Sync Strategy:- Full table (every run reads the current state)
- Primary key(s):
report_id,audience_id,insight_name,key,occurrence
Audience influencers
Audience influencers
Stream name:
audience_influencers. One row per influencer of each audience, in affinity order.Sync Strategy:- Full table (every run reads the current state)
- Primary key(s):
report_id,audience_id,influencer_id
Audience content
Audience content
Stream name:
audience_content. One row per audience that has a content analysis. Not selected by default.Sync Strategy:- Full table (every run reads the current state)
- Primary key(s):
report_id,audience_id