External analytics tags on DealMaker

Introduction

Web analytics providers make it easy for various parties to track the performance of their online presence. Many developers, marketing teams, and other publishers of web content are interested to know the performance of their online assets, as such insights enable them to better their products and services. Web analytics providers like Google, Facebook, and LinkedIn aim to solve this problem by providing lightweight, easy-to-use solutions that enable users to track their content’s performance from a centralized dashboard. At DealMaker, we aim to support these activities by allowing analytics scripts (often referred to as tracking tags, tracking pixels, insight tags, etc.) to be hosted on our platform.

How does it work?

Analytics tags most commonly take the form of compact chunks of Javascript, which site owners publish to their webpages. The script is loaded once a user accesses a page or set of pages, and collects information about the user’s activity in that area of the website. This information is sent by the script to the analytics platform’s dashboard, where the site owner is given insights about user behaviour. Some examples of such insights are:

  • How often a certain page is visited
  • How much time users spend on a page before following a call-to-action or leaving
  • Whether or not users follow a call-to-action when visiting the page
  • Which of a number of paths a user takes when moving through the site

DealMaker is pre-configured to function with Facebook Pixel, Google Analytics services, and LinkedIn Campaign Manager. Follow the workflow below to set up tracking of events on our pages.

Workflow

In the vast majority of cases, the workflow for adding analytics tags to DealMaker’s various webpages begins with an end-user who wants to track Investor/Accountholder engagement with their Deal or KYC Package. For the purposes of this documentation, we’ll use a Deal facilitator who wants to track Investor acceptances at a “Magic Link” (DocumentPackageInvitation). We’ll assume that the Deal and Magic Link have already been created, and dive into the workflow specifically associated with setting up analytics tags:

  • Set up an account with Google Analytics, Facebook Pixel, or LinkedIn Campaign Manager

Use the analytics dashboard to set up a Web Data Source/Property. Facilitators should refer to the documentation provided by Facebook, Google, and LinkedIn for this.

  • Retrieve the unique Analytics ID for your property or data source and send it to your DealMaker Account Manager

On the Facebook Pixel dashboard, this ID is numerical, displayed beneath the Data Source name in the left column.

On the Google Analytics dashboard, this ID takes the format UA-XXXXX-Y and can be found under All Web Site Data > All > Analytics.

On the LinkedIn Campaign Manager, this partner ID is numerical and can be found under Account Assets > Insight Tag > Manage Insight Tag. 

  • DealMaker will integrate your IDs using our existing tracking integrations — no need to provide the team with scripts or further configuration information.
  • Google Analytics users can now track add_to_cart events occurring on the Magic Link page

These events occur when a prospective subscriber accepts the invitation.

Facebook Pixel users can now bind analytics events of their choosing to the Magic Link page

The occurrence and outcomes of these events will depend on the Facebook Pixel configuration.

LinkedIn Campaign Manager users can now track activity on specified page URLs with conversion events

The occurrence and outcome of these events will depend on the user’s conversion configurations, which must track conversions by Page Load

Supported entities on DealMaker

Currently, the following entities on DealMaker can have analytics tags added to them. The location (URL) at which the tags are rendered, as well as any event bindings, are provided in the table below

Entity

Location Rendered

Google event bindings/notes

Facebook event bindings/notes

LinkedIn event bindings/notes

Magic Link

/invitations/:token/view

Accept Invitation button bound to addToCart event.

Bindings are defined via Facebook UI

Track conversions by Page Load