Create Custom "Clicks" with HTTP Post

  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

  • Email: //REQUIRED Email of the lead we are creating the click for
  • IP_Address IP address of where the click originated from
  • Date_Time //REQUIRED Can be a properly formatted Date/Time string or "NOW" to default to the current Date/Time:  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.  
    PLEASE NOTE: PresetOverride values are case-sensitive.
    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

Sample HTML Form for Manually Submitting Custom Click Events

Examples for using Custom "Click" HTTP Post:

Scenario 1 (PresetOverride = LIVE_EVENT)

    • 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

Scenario 2 (PresetOverride = EXISTING_LEADS)

  • 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

 

Scenario 3 (PresetOverride = EXISTING_LEADS)

  • 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

 

Scenario 4 (PresetOverride = REOPTIN_TO_FIRST_OPTIN)

  • 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

 

Scenario 5 (PresetOverride = ORDER_LAST_CLICK)

  • 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