This article outlines the steps to validate and review the data integration process in Grip following the Data Mapping call.
After the Data Mapping call, the integrations team will initiate a single data pull in the Grip platform by an agreed date. We will create a timeline working back from the earliest launch date and based on the complexity of the integration. It is important to review and ensure that the data is flowing correctly into Grip. During your review of the integration, it is your chance to request updates to ensure the data is being presented as you it need.
Data Validation Checklist
To facilitate a smooth integration process, please follow the checklist below:
Attendee, Company, and Product Data
-
Ticket Types:
Confirm that all ticket types are correctly imported into the respective data types in Grip and that only the requested ticket types are present. -
Field Mapping:
Verify that all fields, such as headline, job title, location, and custom profile fields, are mapped as desired. Pay special attention to formatting, arrays, and HTML if applicable. -
Relationships:
Double-check that relationships between representatives, companies, and products are accurately established. -
Custom Groups:
Validate that custom groups are categorizing profiles correctly and appearing as intended on the front end. -
Permissions:
Review permissions to ensure that the appropriate access levels are set for each data type. -
Data Completeness:
Confirm that no data is missing during the integration process, with particular attention to custom profile fields (CPFs).
Meetings
-
Meeting Locations:
Ensure that all meeting locations are available in Grip and correctly linked to the corresponding profiles. -
Default Locations:
If multiple meeting locations are linked to a profile, ensure the correct location is set as the default. -
Additional Locations:
Verify that any additional meeting locations manually added are appearing correctly for the relevant data types.
Sessions
-
Session Fields:
Check that all session fields, including name, description, stage, tags, and other relevant information, are mapped as desired. Pay attention to formatting, arrays, and HTML if applicable. -
Session Timing:
Ensure that the session start and end times are correct. -
Attendance Accuracy:
Verify that session attendance is recorded accurately, if applicable. -
Session Links:
Ensure that all session links are working correctly, if applicable. -
Speaker Linking:
Confirm that speakers are properly linked to their respective sessions, if applicable. -
Track Visibility:
Check permissions to ensure the correct attendee types can see the appropriate tracks. -
Private Sessions:
Review private sessions to ensure the correct attendees can see these sessions and/or have them added to their schedule.
Timeline for Review
To allow sufficient time to address any potential issues, it is advisable to complete the review at least 5 working days before the event launch. This timeline provides time for necessary modifications or troubleshooting before the event begins, ensuring a smooth experience for all participants.
FAQs
When should I start reviewing the data integration?
It is recommended to begin your review immediately after the data pull is completed to allow ample time for any adjustments.
What should I do if I find discrepancies in the data?
If any discrepancies are found, promptly request updates through the Grip delivery/integrations team to ensure data accuracy before the event.
Is there a limit to how many updates I can request?
There is no hard limit, but it is best to request all necessary updates in a single communication to streamline the process.