Conversion pages
List the pages that mean a customer converted, turn on one switch, and Tapper counts a conversion when a visitor reaches one. No conversion script needed.
A conversion page is a page that means a customer converted: an order confirmation, a thank-you page, a booking receipt. List those pages, turn on Count conversions only from these pages, and Tapper counts a conversion when a visitor reaches one. Your monitoring script already sees the page view, so nothing new goes on your site.
This is the alternative to the Conversion script. Use it when your tag manager cannot fire a tag only on the confirmation page, or when you would rather not add a second tag at all.
Where to find it
In the sidebar, open Setup, then Website. If your workspace has more than one protected entity, first pick the one for this website with the switcher under the workspace name. In the list of areas on the left, click Monitoring, then open the Conversions tab.
Workspace owners, admins and managers can add, change and delete conversion pages.
Add a page
Click Add page and fill in the Add conversion page dialog.
| Field | What to enter |
|---|---|
| Name | What this page means to you, for example Order confirmation. |
| Rule | How to match the page. The rules are listed below. |
| Address | The part of the address after your domain, for example /checkout/thank-you. Upper and lower case do not matter. |
| Value (optional) | What one conversion on this page is worth. |
| Currency | The currency of that value, picked from the list, for example USD. Give a value and a currency together, or leave both empty. |
| Counts as a conversion signal | On by default. See Conversion signal below. |
Rules that match the address
- Is exactly: the address is exactly this.
- Contains: the address contains this text anywhere in it.
- Starts with: the address begins with this text.
- Matches pattern is in the list but cannot be saved. Use Is exactly, Contains or Starts with instead.
Only the path is matched. Anything after ? or # is ignored, so an order
id or a campaign parameter in the address does not stop a page matching.
Rules that match the words on the page
Some sites show every outcome at the same address, for example an application page that says approved, pending or declined. Two rules look at what the page says instead of its address:
- Page text contains: the words on the page contain this text.
- Element text contains: the words inside one part of the page contain this text. Use it when only one area shows the result.
With either rule, the Address field becomes Text on the page. Enter the words that appear only when a visitor has converted, for example your application has been approved, and make sure they never appear on a page that is not a conversion. Upper and lower case and extra spaces do not matter. The text can be up to 200 characters long.
Element text contains also asks for Part of the page: the id or class of the area that shows the result, for example #status, up to 100 characters. Your developer can give you this. Native form controls are never read, and an area that is hidden is not read either.
Rules that match the words on the page count only while both Check the words on the page and Count conversions only from these pages are on. Check the words on the page is under the list, and it can be turned on once at least one such rule exists. Deleting the last such rule turns it off. When it is on, the words visible on the page are read in the visitor's browser. The words themselves are never sent to Tapper.
A short phrase can hide inside a longer one: "not approved" contains "approved". When a phrase could also match a decline or pending page, the dialog warns you, and you confirm with I checked the wording on the decline and pending pages before you can save.
When more than one rule matches
The most specific rule counts. Address rules are compared only with other address rules, and rules that match the words on the page only with each other. A longer rule wins over a shorter one. Among address rules of the same length, Is exactly wins over Starts with, which wins over Contains. Between two rules that look for the same words, Element text contains wins over Page text contains. The conversion takes the value of the rule that counts, including no value when that rule has none. The dialog tells you when a new rule overlaps one you already have, which rule would count, and which value the conversion would get when the two values differ.
The same rule twice cannot be saved: the dialog says so and Save stays off.
How often a page counts
One conversion per visitor, per page rule, per day. Days are counted in UTC. A customer who refreshes the confirmation page ten times is counted once.
Conversion signal
Each page has a Signal setting, shown as Yes or No in the Signal column of the list and as Counts as a conversion signal in the dialog. You can change it in the list directly.
- Yes: a visitor who reaches this page is treated as a real customer when Tapper trains its models and checks traffic.
- No: use it for a result that is not a success, such as declined or pending.
The conversion is still counted in your numbers either way.
Count conversions only from these pages
Under the list there is a switch: Count conversions only from these pages. It decides which of the two ways of counting is used.
- While it is on, your conversion pages count. A conversion your site reports with the conversion script is not counted, whichever page the visitor was on.
- While it is off, the conversion script counts and your conversion pages do not.
The switch can be turned on once the list has at least one page. Deleting the last page turns it off.
Turn this on only once your list is complete. A confirmation page you forgot to add is a conversion you stop counting.
Edit or delete a page
Hover a row to show its edit and delete buttons. Deleting a page stops it counting conversions. Conversions already recorded are kept.
Which one should you use?
Best when you already fire a tag on the confirmation page, or when the order value changes per order: the script sends the real value, order id and currency.