As part of the onboarding process with Magnify, you will need to configure your metadata in order for Magnify to understand relationships and linkages between the data in various systems. As listed in our requirements, each system you integrate with Magnify will require a universal identifier that will allow us to create the linkages between those systems.
Overview
After you've integrated your systems and tools with Magnify and data has been successfully ingested, Magnify will provide you with a configuration file for each integrated system. This file contains an export of every ingested object and field. During a joint session, Magnify will work with you to review the file containing the objects and fields within the file to determine where to source the unique identifier.
Additionally, during the configuration, will have the ability to specify any objects and/or fields that should be hidden within the platform.
File Components
You will be provided with a file for each tool or system you have integrated with Magnify. Each file will display object information and fields in separate tabs.
Objects
On the objects tab you will see information populated for which connected system the data is in reference to and the ingested object name. Below is a sample of what you might expect to see in a configuration file (colored text indicates customer identified information):
| Platform | Object Name | Universal Account ID Column | Universal User ID Column | Show in Segment Builder | Object Display Name |
| Intercom |
admins |
TRUE | Admins | ||
| Intercom | tags | TRUE | Tags | ||
| Intercom | teams | TRUE | Teams | ||
| Intercom | segments | TRUE | Segments | ||
| Intercom | companies | company_id | TRUE | Companies | |
| Intercom | contacts | TRUE | Contacts | ||
| Intercom | conversations | TRUE | Conversations | ||
| Intercom | company_segments | TRUE | Company Segments |
To specify the universal account identifier for a particular system, locate the row of the object that contains the universal account identifier and list the column for where that data is stored. In the example above, the universal account identifier within Intercom is stored in a field called company_id, which is the same identifier that is used across all other systems. Once the object and field has been identified for an account, all other fields can be left blank as there should only be a single field for a universal identifier.
Repeat the steps above for the universal user identifier, and for every integrated system.
If you want a specific object hidden from the platform, you can mark the Show in Segment Builder field as False. By default all objects will be set to True and shown within the platform.
If you'd like to rename your objects within Magnify, you can specify those details under the Object Display Name. For example, you may wish to update sfdc_acct_id to display as SFDC Account ID.
Fields
The fields tab will display all of the ingested columns within each object that Magnify successfully processed. These are mainly used for reference and should be reviewed for accuracy.
| Platform | Object Name | Field Name | Display Name | Data Type |
| Pendo | account | accountid | Account ID | character varying |
| Pendo | account |
name |
Name | character varying |
| Pendo | account | lastvisit | Last Visit | character varying |
| Pendo | account | firstvisit | First Visit | character varying |
| Pendo | visitor | accountid | Account ID | character varying |
| Pendo | visitor | id | ID | character varying |
| Pendo | visitor | character varying | ||
| Pendo | visitor | full_name | Full Name | character varying |
| Pendo | visitor | lastvisit | Last Visit | character varying |
If there are fields missing that you expect to see, it is likely due to incorrect permissions with the integration or an error with data ingestion. Please notify support@magnify.io if you notice any issues.
Updated