Note: This action will only submit individual records when triggered. If you need to import historical data, please contact support@wickedreports.com for assistance importing your historical click data or custom events.

There are many scenarios where you were not able to get tracking for a New Lead or an Order and you know how a new lead or an order should be attributed.  There are unfortunately a number of reasons Wicked Reports may not have known how to attribute it. 

For this reason, we offer the ability to create a custom "click" inside Wicked Reports.  Here's a few examples of how this could be used

  1. You go to a marketing event and collect new leads and import them into your CRM.  After importing these leads to your CRM, you can set the First Optin Attribution for them.
  2. You purchased and email list and import all the contacts into your CRM.  After importing these leads to your CRM, you can set the First Optin Attribution for them.
  3. You signed up for Wicked Reports and have a number of contacts who already exist and you know exactly where you found those leads.  You can set the First Optin Attribution for them.
  4. You want to track future funnel steps back to the original source of the contact. 
    1. Example:  Your funnel brings in new leads through Facebook.  After a number of steps in your funnel, your contacts need to book a call with your team and you want to be able to see how many Calls were booked from these Facebook Ads.  You can create "Re-Optins" for the original First Optin of the contact.  In this scenario the Re-Optin count for the Facebook Ad would be a good indicator of Calls that were booked later.
  5. You received orders from a source and did not have tracking on the links or there was simply no click to track.  You can set the Last Click Attribution for a customer's MOST RECENT order.

How To Create Custom Clicks


These custom Clicks can be created using an HTTP Post.  HTTP Posts are common in CRMs.  You can typically trigger them through Automation options in your CRM (Infusionsoft Campaigns, ActiveCampaign Automations, etc.)

URL:  https://api.wickedreports.com/clicks/<clientname>      //your clientname can be found on the settings page

Name/Value Pairs

Name values are Case Sensitive, so be careful

  • Email: //REQUIRED Email of the lead we are creating the click for
  • IP_Address IP address of where the click originated from
  • Date_Time (provide date/time or NOW):  This is a Date/Time setting for when to create the clicks. You can use “NOW” to use the current date/time.  Date/Time Format (mm/dd/yyyy hh:mm am/pm)
  • Timezone: //REQUIRED Timezone of Date/Time provided.  This would be the timezone your CRM is using, NOT the Timezone of the Contact.  (EST Timezone="UTC-5", CST Timezone="UTC-6", etc)
    • Example:  Infusionsoft uses EST (UTC-5)
    • If you are using a PresetOveride EXISTING_LEADS or ORDER_LAST_CLICK, you can use "UTC-0"
    • Timezones change with Daylight savings time.  For example, EST (Eastern Standard Time) is UTC-5 part of the year and UTC-4 part of the year.  If you are setting up an automation that will run continuously, you will need to be aware of this and make sure your automation updates when daylight savings time occurs.
    • NOTE: If you used NOW for Date_Time, you should use UTC-0 for Timezone.
  • TimeOffset: The number of minutes to subtract from Date/Time provided.  
    • Example: If you know there's a 20 minute delay for when the click is getting created and you want it to appear 20 minutes ago, you could use 20 as your TimeOffset.
  • Source: The utm_source value that will be applied to the click
  • Campaign: The utm_campaign value that will be applied to the click
  • Term: The utm_term value that will be applied to the click
  • Medium: The utm_medium value that will be applied to the click
  • Content: The utm_content value that will be applied to the click
  • PresetOverride: //REQUIRED Predefined reasons for using this method to make this HTTP Post easier to use.  The Valid PresetOverride Options are:
    • LIVE_EVENT
      • Use a Date/Time that is the early morning of the first day of the event.
      • If the click shows up EARLIER than the create date of the the contact in Wicked Reports, we will use the UTMs provided to set the FIrst Optin Attribution for the contact
      • If the click shows up LATER than the create date of the the contact in Wicked Reports, we will use the UTMs provided to create a Re-Optin for the contact.
    • EXISTING_LEADS
      • We will use the UTMs provided to set the FIrst Optin Attribution for the contact
    • REOPTIN_TO_FIRST_OPTIN
      • We will create a Re-Optin using the contact's current First Optin attribution.  The Re-Optin will be created using the Date/Time provided along with the TimeOffset.
    • ORDER_LAST_CLICK
      • We will use the UTMs provided to set the Last Click attribution of the Contact's most recent order
    • OTHER
      • Creates a click for the contact, at the time provided with the UTMs provided



IMPORTANT:  Timezones change with Daylight savings time.  For example, EST (Eastern Standard Time) is UTC-5 part of the year and UTC-4 part of the year.  If you are setting up an automation that will run continuously, you will need to be aware of this and make sure your automation updates when daylight savings time occurs.

Sample HTML Form for Manually Submitting Custom Click Events

You can use this code sample, referencing the specifications above and the examples below, to create a web form that will manually submit HTTP Post Custom Click events.

<form id="form-submit-test" action="
https://api.wickedreports.com/clicks/<YourClientName>" method="post" target="_blank">
  Email:<br>
  <input type="text" name="Email" value=""><br>
  IP_Address:<br>
  <input type="text" name="IP_Address" value=""><br>
  Date_Time:<br>
  <input type="text" name="Date_Time" value=""><br>
  Timezone:<br>
  <input type="text" name="Timezone" value=""><br>
  TimeOffset:<br>
  <input type="text" name="TimeOffset" value="0"><br>
  Source:<br>
  <input type="text" name="Source" value=""><br>
  Campaign:<br>
  <input type="text" name="Campaign" value=""><br>
  Term:<br>
  <input type="text" name="Term" value=""><br>
  Medium:<br>
  <input type="text" name="Medium" value=""><br>
  Content:<br>
  <input type="text" name="Content" value=""><br>
  PresetOverride:<br>
  <input type="text" name="PresetOverride" value=""><br><br>
<button type="submit" form="form-submit-test" value="Submit">Submit</button>
</form>


Examples for using Custom "Click" HTTP Post:

Scenario 1 (PresetOverride = LIVE_EVENT)

I attended an event of some kind and collected a number of leads.  Either they were already entered into my CRM at the event or I want to import these leads into my CRM.  Since I know where I collected these leads, I want to make sure I can show that the lead was collected at the event by setting the Contact's First Optin attribution, if they are a new lead or creating a Re-Optin if they are an existing lead.

You will likely trigger automation based on a Tag that has been applied to these contacts.  You can set up your HTTP Post with the Following Values

  • Email: Contact's email address
  • IP Address: 
  • Date_Time:
  • Timezone: "UTC-0"
    • This is a required field but we are not using it with the LIVE_EVENT PresetOverride, so it does not matter what you use
  • TimeOffset:
  • Source: Traffic and Conversion Summit 2018
  • Campaign: Lead Generation
  • Term: Event Attendees
  • Medium: Booth
  • Content: Booth
  • PresetOverride: LIVE_EVENT

Note: The values provided here are basic examples of UTMs.  If your leads didn't come from an booth at a live event, you can use whatever Source, Campaign, Medium, Content and Term make sense for your scenario

Here's what it would look like in Infusionsoft using a Send HTTP Post action in an automation sequence.



Scenario 2 (PresetOverride = EXISTING_LEADS)

I recently started using Wicked Reports and have thousands of leads with no First Optin Attribution.  I know that many of these leads came from a specific Facebook campaign called "My Facebook Campaign".  I would like to have those leads attributed to this campaign so that future revenue from those leads can be attributed to Facebook.

You will likely trigger automation based on a Tag that has been applied to these contacts.  You can set up your HTTP Post with the Following Values

  • Email: Contact's email address
  • IP Address: 
  • Date_Time:
  • Timezone: "UTC-0"
    • This is a required field but we are not using it with the EXISTING_LEADS PresetOverride, so it does not matter what you use
  • TimeOffset:
  • Source: Facebook
  • Campaign: My Facebook Campaign
  • Term:
  • Medium: PPC
  • Content:
  • PresetOverride: EXISTING_LEADS
Note: The values provided here are basic examples of UTMs.  If your leads didn't come from Facebook, you can use whatever Source, Campaign, Medium, Content and Term make sense for your scenario


Scenario 3 (PresetOverride = EXISTING_LEADS)

I recently purchased an email list with thousands of leads.  The list I purchased is called "Steve's Contacts List".  I would like to have those new leads attributed to "Steve Jones Contact List" so that I can determine the real value of the leads acquired from this list, over time.

You will likely trigger automation based on a Tag that has been applied to these contacts.  You can set up your HTTP Post with the Following Values

  • Email: Contact's email address
  • IP Address: 
  • Date_Time:
  • Timezone: "UTC-0"
    • This is a required field but we are not using it with the EXISTING_LEADS PresetOverride, so it does not matter what you use
  • TimeOffset:
  • Source: Steve Jones Contact List
  • Campaign: Purchased List
  • Term: Steve Jones List
  • Medium: Email
  • Content: Purchased List
  • PresetOverride: EXISTING_LEADS
Note: The values provided here are basic examples of UTMs.  If your leads didn't come from a purchased email list, you can use whatever Source, Campaign, Medium, Content and Term make sense for your scenario


Scenario 4 (PresetOverride = REOPTIN_TO_FIRST_OPTIN)

I run Facebook Ads to generate new leads.  Once my leads have opted into my list, they are entered into my funnel.  One step of my funnel is to get the leads to book a call with my sales team.  What I really want to know is how many calls are actually booked by the leads coming from each of the Facebook Ads. The result of this strategy will be to increment the Re-Optin count of the Facebook Ads after calls are booked.  So, to know how many calls were booked, you would end up using the Re-Optin count from the Facebook Ads.  This will not be 100% exact because any actual re-optins from those Facebook ads would also be counted in the Re-optins,so be aware that there will be a variance for this number

You will likely trigger automation based on a Tag that has been applied to these contacts after the call is booked.  You can set up your HTTP Post with the Following Values

  • Email: Contact's email address
  • IP Address: 
  • Date_Time:  NOW
  • Timezone: "UTC-5"
    • I am using UTC-5 because Infusionsoft represents data in EST.  If your CRM uses a different timezone, you will use that value
  • TimeOffset:
  • Source: 
  • Campaign:
  • Term:
  • Medium:
  • Content:
  • PresetOverride: REOPTIN_TO_FIRST_OPTIN
Note: Remember that the Re-Optin count will only be a good representation of the calls booked from the original Facebook Ads because actual Re-Optins from your existing leads will also force the Re-Optin count to go up. 


Scenario 5 (PresetOverride = ORDER_LAST_CLICK)

As part of my sales cycle, our leads will have a call with our sales team.  When sales occur, I want the call and the sales rep they spoke with to be the Last Click attribution for them.  

You will likely trigger automation based on a Tag that has been applied to the contact after a sale occurs.  You can set up your HTTP Post with the Following Values

  • Email: Contact's email address
  • IP Address: 
  • Date_Time:
  • Timezone: "UTC-0"
    • This is a required field but we are not using it with the ORDER_LAST_CLICK PresetOverride, so it does not matter what you use
  • TimeOffset:
  • Source: Sales Call
  • Campaign: Sales Call
  • Term: Sales Call
  • Medium: Sales Call
  • Content: Jim Stevens
    • I am using the name of the sales rep in the Content value as an example of how to represent the sales rep
  • PresetOverride: ORDER_LAST_CLICK
Note: The values provided here are basic examples of UTMs.  You can choose to use whatever makes sense for how you want to represent the call in your reporting.  In this scenario, we would be setting the Last Click attribution for the most recent order of the contact provided