Implementation User Role Guide

It's important to plan your Monetate JavaScript API deployment with all the team members who'll be involved in using Monetate in your organization. When all the stakeholders get together during the planning stages, you can set clear goals and expectations of what the business user can do within the Monetate platform.

Recommended Internal Team Members for Planning

  • Business owner
  • Project manager
  • Engineer(s)
  • QA personnel

The recommended baseline JavaScript API deployment includes the method calls that unlock many the platform's capabilities. See What Do You Want to Do on Your Site? for a complete listing of what features the API unlocks in the platform and how you can leverage them for experiences.

JavaScript Development

The first step to tracking your site data is putting the right person in charge of completing it. Typically, this person should be a software engineer, a back-end developer, or someone who has experience with JavaScript who can tag your site with Google Tag Manager or similar tagging systems.

Ultimately, the person who completes the process must possess these qualifications:

  • Install and use the Monetate Inspector browser plug-in
  • Have the necessary access to modify site templates
  • Be able to request page-specific data from your server (for example, a list of product IDs shown on the current page)
  • Have enough familiarity with JavaScript to make API calls

The time required to complete the implementation depends on the technical complexity of your site, the number of different page types/templates, the complexity of the data you want to report, and how easy it is to query your site's back end for that information.

As a rule of thumb, an engineer familiar with your site should need about 10 to 12 hours of undivided attention to complete the necessary development for the baseline Monetate JavaScript API.

QA Testing

The next step in the process involves performing QA testing. It should be performed by someone who has experience similar to the person who added the method calls or by a QA professional or a marketer who is very familiar with your site. Most importantly, QA testing should be completed by someone other than the person who added the method calls to your site.

The key to successful QA testing of your site is to check that all templates and page types that should pass data to Monetate are doing so correctly.

Ultimately, the person who completes QA testing must do the following:

  • Use the Monetate Inspector to verify the accuracy of all the reported data
  • Complete a conversion on your site, if that is important to your business

The time required to complete QA testing depends on the technical complexity of your site, the number of different page types/templates, the complexity of the data you want to report, and how easy it is to query your site's back end for that information.

As a rule of thumb, a person familiar with your site should need about 4 to 6 hours of undivided attention to complete QA testing.

API Deployment to Production

After you complete QA testing your site's Monetate JavaScript API in your development environment, you can move the API code to production.

Ultimately, the person who completes the deployment to production must meet these qualifications:

  • Have the necessary access to modify site templates
  • Be able to deploy tags to your site via the tag management system