Each action needs to be configured individually. Hang in there and we'll get through this as soon as possible.
The way we distinguish between which products were purchased is by the product Id.
Lookup all Product IDs
Complete the attached worksheet to store all of your product IDs so you can reference them throughout this article.
Where do I find my product IDs?
Set Actions to "Advanced"
Each action can be either "simple" or "advanced" which changes how the action is counted.
- Simple: Action is counted when the action is between two pages and the users goes from page A to page B. No other conditions.
- Advanced: Action is counted when the action is between two pages and the visitor goes from page A to page B AND the script was triggered on page A.
If the action is only connected to one page, the advanced action is counted when the event snippet is triggered on page A.
In this case we'll set each action in Funnelytics to be advanced.
Go to the action settings > tracking > and choose advanced.
An acceptable exception is the complete form action between an optin page and the next page. In that case, where it's assumed they had to complete the form to go from the optin page to the next page, you may leave that as simple. It would also be acceptable to leave the purchase on OTO 1 to OTO 2 page as simple if you wish.
Enter The Event Name
Each action needs to have an event name. The event name represents the category of event that is happening. This is normally customizable to your liking, but if you're using the scripts provided to track ClickFunnels, you have to use these events names specifically.
All the purchase actions will have the same event name of purchase.
If you're tracking a form submission (either an optin or the form on step 1 of a multi-step form) the event name should be form-submit.
To track if the user clicks 'no' on an upsell/downsell page, the event name of that action should be reject-click.
Add Event Properties
To identify a specific event in Funnelytics, we're going to add event properties to each event.
Each purchase event should have a property where the key is
prodId and the value is the actual product Id.
For example, to track your main product purchase, you would enter the product Id of the main product.
Hopefully you can refer back to the worksheet from earlier to access all your product Id's easily.
Purchase Events Alternative: (you can use either/or both)
The above method allows you to track 1 product purchase per action. Use this method instead to have 1 action represent a combination of products. For example you may want 1 action the represents if the visitor purchased the main product AND purchased the bump instead of tracking those as two separate products.
All you need to do is change the property to have a key of the product ID and a value of either true or false depending on if you want represent that the product was purchased or not.
In the example below, this one action now represents if the visitor purchased the product with ID 123 AND the product with ID 456.
Form Submit Events:
There are two possible types of form submit events. The first is an optin page, where the only thing to do on the page is submit a form. The second is completing step 1 of a multi-step form.
To track a single optin page you should add a property with a key of
formTitle and the value of the
formTitle variable you declared on the optin page. Remember, we declared the
formTitle variable in step 1 of this guide series.
Alternatively, as mentioned earlier, this may be a simple action in which case no further action is required.
To track the second type of form submit, the first step of a multi-step form, you should set the property to have a key of
formStep and a value of
Lastly, to track the events that symbolize the visitor rejecting to accept our addon product offer, we use a reject-click event.
To track these 'reject-click's, all you need to do is include a property with a key of
product and a value of
Before Moving On
Ensure the following is complete before moving on to the next step of the setup process:
- Each advanced action should have an event name and defining properties. If it's a purchase, the value should match the actual product Id. The complete form should be the formStep or the formTitle depending on where the form is. The reject-click event is always a static value of
Now that everything is setup, let's run through our funnel in test mode and make sure that it's working as expected.
If you have any questions or need further clarification with setting up actions, remember to reach out to our support team anytime by clicking the support icon in the bottom-right corner of your dashboard, or emailing us at email@example.com we are always ready to assist you!