Overview
If your organization uses KORE DWA, you can access your Helix data directly using SQL via DWA. Although this isn't necessary for all users, it enables advanced users to write powerful queries for specialized purposes.
Example use cases for leveraging helix data out of DWA:
- Leverage Tags, Attributes and Audiences as filters to any report or analysis project you have built on DWA.
- For example, if you have a Tableau dashboard tracking ticket sales transactions and a Helix tag for past season ticket buyers and a Helix audience identifying upsell targets, you can now easily add a filter on the Tableau report for the past season buyer tag or the upsell target audience and segment your report to show how many returning members or upsell targets made a purchase.
- Another example includes, if you have a Helix audience for at-risk accounts and a Tableau report built using your data warehouse that shows live attendance data, you can add the at-risk audience to that report so when they show up a team member greets at their seat.
- Leverage DWA's ability to create extracts out of the database into AWS s3 bucket for downstream applications to consume.
- For example, you create an audience of e-commerce buyers that live in your market but are not ticket buyers and do not currently have an open ticket sales opportunity. This audience will automatically refresh and sync into your data warehouse nightly. From here, you can set up an extract to an AWS s3 bucket that is connected to your email marketing tool, like Salesforce Marketing Cloud or Eloqua, to pick up that data and automatically put it into a marketing journey.
Connect to your data warehouse as usual. The data is stored across nine tables within the helix
schema.
ERD (Entity Relationship Diagram)
Note: DWA uses Amazon Redshift, which does not enforce table constraints such as uniqueness of every row or primary key. The "PK" (private key) and "FK" (foreign key) notations in this diagram are solely for ease of use.
The grrecords
table contains the same fields you defined during setup in addition to a system-generated ID string and timestamps. The attributes
, tags
, audience
and mappings
tables use that ID (gr_id
) to associate any number of rows with a particular Golden Record. There is not a limit for how many tags, attributes, and data set records a Golden Record may connect to.
Data dictionary
(see attachment at the bottom of the page)
*Note: custom fields created on the golden record will be included in the grrecords
table using the field's API name.
Table name | Refresh frequency | Refresh method |
attributes |
daily | Full refresh (wipe and replace) |
attributesmeta | daily | Full refresh (wipe and replace) |
audience | daily | Full refresh (wipe and replace) |
audiencemembership |
daily | Full refresh (wipe and replace) |
grrecords | daily | Full refresh (wipe and replace) |
integrationlogs | daily | incremental updates |
mappings | daily | Full refresh (wipe and replace) |
tags | daily | Full refresh (wipe and replace) |
tagsmeta | daily | Full refresh (wipe and replace) |