This article will help you learn about how Daasity replicates data from Emplifi, limitations to the data we can extract and where the data is stored in the Emplifi schema
Key Topics:
Click on the links below to take you to the section where you can learn more about this Integration
- Integration Overview
- Integration Availability
- API Endpoints
- Entity Relationship Diagram
- Emplifi Schema
- Related Resources
Integration Overview
Emplifi is a unified CX platform that combines marketing, care and commerce together to help businesses create quality customer experiences. It provides insights and analytics for every touchpoint on the customer journey.
This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.
Integration Availability
This integration is available for:
- Pro
NOTE: As the majority of Emplifi tables are created dynamically based on the dimensions and measures selected there is no out-of-box transformation or visualization for this integration.
API Endpoints
The Daasity Emplifi extractor is built based on this Emplifi (Social Bakers) API Documentation. The following endpoints are used by Daasity to replicate data from Emplifi:
Entity Relationship Diagram (ERD)
The embedded diagram houses the ERD for the Daasity Emplifi integration illustrating the different out-of-box tables and keys used to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.
Emplifi Schema
The Daasity Emplifi extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
Note: The default tables in the Emplifi schema use the Posts API. The Profile Metrics and Aggregated Post Metrics API generate custom tables within the Daasity platform
Custom Reports (Metrics Endpoint)
This endpoint is a custom endpoint that must be configured within the Daasity App - review this article on how to setup custom reports
The integration runs on a daily basis with a primary and secondary extract:
- Primary Extract: the integration extracts all the Profiles that are available within each platform
- Secondary Extract: the integration extracts the dimensions and metrics as specified in the integration setup for each profile within each platform
The Emplifi integration has certain limitations as outlined here:
- Can only extract 12 months of history at one time
- Limited to 25 metrics per report
CAUTION: The Daasity integration with Emplifi only extracts data from the six (6) supported platforms in the Profile Metrics section of the Data API
All custom tables generated by the Emplifi integration will be created in the [emplifi] schema within the database.
- Update Method: UPSERT
The table name and definition is based on the selections made when setting up each report within the Daasity app. Every report will have at a minimum the following fields:
| Emplifi Field | Database Column |
| date.day | date_day |
| profile | profile |
Additional metrics and dimensions can be selected based on the platform selected:
NOTE: When selecting additional metrics and dimensions, you can only select one dimension noted with a * and you can only select metrics with dimensions that are listed in the Social Bakers documentation above
Profiles Table
The [profiles] table is generated by requesting a list of all the profiles connected in Emplifi for each platform by using the List of Connected Profiles endpoint
This is the first extract run on a daily basis to determine if any new profiles have been added to Emplifi
- Update method: UPSERT
- Table Name: emplifi.profiles
| Emplifi Field | Database Column |
| id | profile_id |
| N/A - determined based on the {network} passed into the API call | social_platform |
| name | name |
| timezone | timezone |
| insights_enabled | insights_enabled |
Posts Table
Posts, Post Labels and Post Attachment tables are generated for 4 of the 6 supported platforms as two of the platforms do not provide any meaningful data.
The [social_platform_posts], [social_platform_post_label] and [social_platform_attachments] tables are generated by using these four endpoints:
Posts
- Update method: INSERT
- Table Name: emplifi.social_platform_posts
NOTE: Post Metrics are captured daily and use an insert so trends on how a post has performed over time can be measured. Thus to capture the current performance of a post you must select the most recent row from the table.
To see performance over time make sure to include the __sync_date in your reporting which identifies when the data was captured
Post Labels
- Update method: UPSERT
- Table Name: emplifi.social_platform_post_labels
Post Attachments
- Update method: UPSERT
- Table Name: emplifi.social_platform_posts_attachments
Aggregated Metrics
Aggregated metrics extracts are created dynamically through a support request to the Daasity team - please contact support@daasity.com to setup your aggregated metrics. The tables are generated by extracting data from the Aggregated Post Metrics API which must be configured for the specific metric and level of detail desired.
Each metric will be stored in its own table and can at one of two levels of detail, either at the profile level or at the profile / post label level
Profile
Tables names as [metric_profile] are at the profile level of detail and will have daily results across all platforms for that metric and profile
- Update method: UPSERT
- Table Name: emplifi.metric_profiles
Profile Post Labels
Extracts at the profile / post label level of detail will generate two tables for each metric.
[metric_profile_post_label] for daily results across all platforms for that metric at the profile and post-label level of detail- Update method: UPSERT
[metric_post_label] which contains the post labels for each profile
- Update method: UPSERT