Implementation & Setup

Let’s start with a crucial differentiation, before diving in: setup vs implementation & migration. It is critical for the success of your project to keep these two definitions in mind, because they are often confused and lead to incorrect expectations.
JENTIS setup:
This is the basic requirement for the JENTIS tracking to work and includes the correct implementation of your individual JavaScript and A-Record.

JENTIS migration:
After the JENTIS setup is complete on your website, your tools, tags and triggers can be moved to the JENTIS tag manager (JTM) and connected to your CMP. We define this process as the JENTIS migration.

FAQs

What does the setup process look like?
Your Customer Success manager  will share your individualized JavaScript tracking codes and A-records with you. For each main-domain, there will be one version. These need to be implemented by your team or agency. Upon confirmation that these steps were completed, our cloud team finalizes your cloud setup.

How long does the setup process take?
This depends mostly on your resources and speed of implementing the JavaScript(s) natively in your website and setting the appropriate A-record(s). In our experience this can vary between less than a day to (unfortunately) a couple of weeks. On our side, the setup is completed in less than one working day.

What does the migration process look like?
This is not easy to generalize because the migration process is geared towards your individual needs and also depends on what and how you have tracked so far. Regardless, here are a couple of “milestones” during the JENTIS migration process.

1. Status quo
2. Definition tracking roadmapIn this next phase a roadmap is defined during which the current setup is consulted – essential parts will be migrated while old or outdated parts can be omitted to speed up and simplify the migration process.
3. Migration – tool by tool. The implementation of each tool, tag and trigger is the next phase – the real implementation phase. Depending on your needs, speed/risk and tracking roadmap this can take anywhere from a couple of days to a couple of weeks to be fully complete. The most important tools can be migrated first to see results soon.
4. Validation & control
   After the implementation of each tool you are required to check the data quality and setup in order to finalize your individual migration.

How long does the migration process take?
As already suggested, it is quite hard to give you an exact estimation here because your individual migration is dependent on various factors ranging from the complexity of your setup, to the number of tools you use and also to the “risk” you’re willing to take in the process.

The migration process can be minimized with the right tracking roadmap in which it is clearly defined what is needed from the old tracking implementations and what is not required. Based on our experience, because of the huge amount of templates in the JENTIS Tag Manager, the migration is a lot quicker than in other comparable tools.

A rough estimation can be given during the first /second meeting with your implementation partner in our experience.

How much effort (time and resources) is required?
You can calculate with the following resource pools: Kick-off meeting and tracking roadmap coordination, regular meetings during the project if desired, control of data and tools after setup.

The migration per se is usually handled externally via a certified JENTIS agency.

Are you offering support?
We at JENTIS are always inspiring to provide our clients with a seamless onboarding process. For this reason, we built our product in a way that enables implementation partners with the easiest possible migration of any server-side tag management system.

As a tool provider, we want to use our resources as much as possible to improve the product, while we let your agency or our implementation partner do what they do best. When required we provide support in the form of documentation, how-to videos, special tracking education workshops and even meetings.

Golden rule for the JENTIS Migration

The cleaner your current tag management is and the more specified we can define the migration of the relevant tools, tags and triggers, the faster the whole process will be finalized.