The Click Search report allows you to search for particular visits/leads and review what happened for each visit and its associated Click ID.
The query criteria is broken into three sections by tabs.
Search last N Clicks
You can review the last 1 to 250 clicks by moving the slide bar to the desired number. Use the mouse to drag the slide bar indicator or tab to the slide bar and use the arrow keys to move left or right.
When you are first getting started 10 clicks should be a good choice. As your volume grows you might need to select more clicks per inquiry. When the results are displayed you can use in-grid filters to find the desired clicks.
Search by ID
Enter one or more IDs separated by a newline, comma, space, semicolon, or tab.
The entered IDs must all be of the same type which you select via the radio control above the text area where you enter one or more IDs.
Search by Other
Click ID - This is the large integer that our system generates when a new visit is started for a given lead.
Form Submission GUID - This is the 36-character Globally Unique Identifier (GUID) that our system generates for each form submission received, e.g. "5302a24f-9c2e-4011-b043-641c3a647710".
Ping/Post GUID - This is the GUID that our system generates for each ping or post consideration during the execution of a ping tree.
Lead Buyer's Response Unique ID - This is the unique identifier that a lead buyer or other type of interface may return. You must have properly mapped this part of their response in the interface configuration and the interface must have returned a value.
For all other searches you must first enter a Start Time and an End Time; the time zone is selected above the tab area. The Start Time is inclusive while the End Time is exclusive. For example, to report against a single day's worth of data select that date at 12:00 AM for the Start Time and the following date at 12:00 AM for the End Time.
After specifying a date/time range at least one other search criteria must also be specified.
Search Substring - To find leads where certain Form Field values were submitted enter a whole or partial value, e.g. "123 Elm St".
IP Addresses - To restrict the results by IP Address enter one or more IP addresses (v4) separated by whitespace, commas, or semicolons e.g. "188.8.131.52, 184.108.40.206". This criteria looks for exact matches. If you need to do a partial match leave this field blank and then use the in-grid filter features against the returned results.
Click Errors - To return Clicks with click errors check this checkbox. For example any attempt to start a click without a promotion ID or with an invalid promotion ID value is a click error.
Invalid Ping Trees - To return Clicks with invalid ping tree errors check this checkbox. Any attempt to do a submit without a ping tree ID or with an invalid ping tree ID value is an invalid ping tree error.
Site ID - To return Clicks that have a particular Site ID as part of their tracking signature enter that value here. This criteria looks for exact matches. If you need to do a partial match leave this field blank and then use the in-grid filter features against the returned results.
Promotion ID - To return Clicks that have a particular Promotion ID as part of their tracking signature enter that value here. This criteria looks for exact matches. If you need to do a partial match leave this field blank and then use the in-grid filter features against the returned results.
Affiliate ID - To return Clicks that have a particular Affiliate ID as part of their tracking signature enter that value here. This criteria looks for exact matches. If you need to do a partial match leave this field blank and then use the in-grid filter features against the returned results.
Returns Mode - Only available if you have the optional Returns Module. If you check this box, the search criteria pane will stay opened after a search and only receivable events will be shown under each click event. This substantially reduces the amount of scrolling necessary when processing multiple returns via the ClickSearch page.
Matching visits/leads will be returned in a pagable grid which can be further filtered using the in-grid filter controls underneath the column headings. To further filter the results enter a value into one or more in-grid filter control boxes and then click the funnel icon to the right of each text box. Choose a match criteria such as "EqualTo" or "LessThan" or "Contains". See How to User Grid Filter Toolbar for more information on filtering.
The IP Address column contains all IP Address values encountered during the visit as well as any unverified IP Address values posted via the "ip" System Parameter. There is a flag next to every IP address which indicates in which country the IP address is located. If you hover over the flag, you will see the country code, name of the country, and if available, the locality.
The Form Field Values column contains one set of Form Field Values for every Submit done during the visit with multiple sets separated from each other by a bullet (•).
To explore a particular visit click the > symbol in the left most column. This will display a summary of all of the events raised during that visit in the order that the event started.
To explore the details for a specific event click the "Event Type" link.
When viewing event detail it is possible to view the raw HTTP request that triggered that event plus the system's resulting response by clicking the GUID hyperlink next to the "Raw Http Request Guid" label. Note that raw HTTP data is considered diagnostic data and has a shorter retention period than other runtime data. See the service agreement for details. Note also that all HTTP headers are reconstructions and are not guaranteed to be 100% correct. This is because the system code that captures HTTP headers runs at an application level while the web server and firewalls of our network may very well add, update, or delete any header or rearrange headers. As-is the headers are still useful... just know that they may vary from reality... most likely in terms of their order in the real request or response.
The Post event (a.k.a. PingPost) also supports viewing its raw HTTP post and response, if applicable, by clicking the GUID hyperlink next to the "Ping Post Guid" label. As with Raw HTTP request/response data the raw HTTP data for a ping/post events is also considered diagnostic data and has a shorter retention period than other runtime data. See the service agreement for details. Note also that like raw HTTP request/response headers all ping/post HTTP headers are also reconstructions and are not guaranteed to be 100% correct. As-is the headers are still useful... just know that they may vary from reality... most likely only in terms of their order in the real request or response. There is also another difference with ping/post raw HTTP captures: Only the last hop is captured. So if a response contains a Location header which indicates a redirect URL then that redirect URL is followed until a non-redirect response is encountered, provided that the system does not determine that the redirect chain will never end, and only the final HTTP response is recorded.
If you have the optional Returns Module, you will see the Request Returns button on each receivable line as pictured below. If you click on that, you can enter a return reason and comment and then mark the receivable as having a return requested. The request will then appear on the "Process Returns" tab on the returns page.
How to User Grid Filter Toolbar