A data model is a representation of entity relationships, designed to create a shared model for designers, developers, data scientists and others. It explains, how the data supposed to come in along with the validation test cases, which can be used by any downstream systems (e.g., segmentation tool). The process goes through three steps:

Step 1: Open up the fields for segmentation

Step 2: Open up the fields for personalization

Step 3: Open up the fields for conversion attribution: To understand the conversion attribution, let’s take some examples.

Example 1: FirstHive is running a campaign; how does it measures the success of campaign – is there any parameter? No! FH is just the platform, it’s the customer who can only define the conversion – FH has no role to play in this.

Example 2: A client is opening a new store. They send email to a list of people, run Google ads, Facebook ads, make announcement on the radio, give ads in the magazine about the exciting offers. The thing is, which of these mediums actually helped get conversions is called attribution. And, the fields that will tell that these many numbers of people are converted and on what basis – you can go and attribute that on this campaign the conversion has happened.

Where is the Data Residing?

The data has to be in FirstHive – if not in FH, then it is not a proper FirstHive deployment.

How to Determine Implementation Happened the Way Intended?

You can check if the implementation has happened the way it is intended, by performing the following sanity checks:

1^st Sanity Check

The data has to be in FH – if not in FH, then it is not a proper FH deployment.

2^nd Sanity Check

Whether you have the ability to build out the segment the way you want to.

For example, if you want to create Dynamic Segments:

Create –> Go ahead –> Play from the frontend –> Define rules to create –> What are the use cases you want to deploy

3^rd Sanity check

Are you able to run campaign across any of these channels? Check if the integrations are working.

4^th Sanity Check

Check the analytics, whether you are running a campaign to capture clicks or any campaign. For example, mobile app integration – you need to run the test campaigns, see the analytics, and verify if all the relevant analytics running are coming up here. All of these are a part of internal UATS.

5^thSanity Check

CPM Login to firsthive.com. For a customer, there should not be any CPM login on the MicroSite. The CPM has to login on FirstHive, there is no other way out.

There has to be SSO implemented, the admin needs to login into FH. The entire data has to be there and from within FH, if they want to take it to MicroSite, there is built-in single click SSO for the same. However, the CPM has to login on FH, the link on the button left.

6th Sanity Check

Post Implementation before go live. Verify if the event data is showing up in the super admin dashboard. This is not FirstHive is doing right now.

For example, you need to check:

What are the UAT events there?
Are they showing up in the super admin dashboard (yes/no)?

These are the key points that needs to be checked before going live.

NOTE

Super admin dashboard is currently under Finance and Product Team, this will be available to others within a few months.