Transaction Inquiries

Transcription

1 Transaction Inquiries Publisher guide 3/26/2014 A guide to Tradedoubler s Transaction Inquiries system for publishers

2 Contents 1. Introduction How it works Accessing the interface Creating a new claim Creating multiple claims Review updated claims Export claims... 8 Appendix A Claims file specification... 9 Appendix B Status list... 10

3 1. Introduction This guide provides details on how to create and manage transaction inquiries via the Tradedoubler interface. An API (Application Programming Interface) integration is also available. Details can be found on the Tradedoubler and Developers site ( 2. How it works When you create a transaction inquiry Tradedoubler will perform a number of quality checks before sending it to the advertiser. This step ensures that all required information is present, that you have a valid connection with the program and that the transaction cannot be found in Tradedoubler s transaction database. The claim is then passed to the advertiser for review and will enter a pending state. Inquiries must be resolved (approved/denied) by the advertiser within this pending period or they will become auto-approved. The pending period for transactions is 60 days. Approved claims are moved to your standard reports as a normal transaction. When denying claims the advertiser is required to select a reason. These claims will remain in the Transaction Inquiry area and will not be moved to your standard reports. This ensures clean reporting with only approved claims being visible in transaction reports. 3. Accessing the interface Log in to your Tradedoubler account as normal and select Tools / Transaction Inquiries from the menu system:

4 If this menu option is not enabled for your account please contact your Publisher Manager or the Publisher Support Team. You will be sent to the Claims tab where you will see all existing claims: 4. Creating a new claim Click on the Create Claim tab and you will see the form for new transaction inquiries:

5 Mandatory fields are identified by an asterisk (*). There are some important points to note about the form: Website: You will only be permitted to enter a site ID or name which is associated with the account you are logged in as. As you begin to type your site ID or site name you will be provided with predictive results based on you available sites. Program: You will only be permitted to enter a program ID or name for those that have a valid connection with the site chosen in the Website field. As you begin to type a program ID or name you will be provided with predictive results based on available programs. Order reference: This is the unique order number/reference provided by the advertiser at the time of transaction. Product name: This is the product name or description of the product(s) in the transaction. This may help the advertiser validate your claim. Order value: This must be numerical, must not include any currency symbols and can only use a decimal point (.) as a separator (thousand separators are not required). Tax and shipping should not be included in the order value. Transaction date: This is the date the transaction took place.

6 Tracking url: You can enter the Tradedoubler click tag as evidence. EPI and EPI 2: If you use the EPI values for attributing transactions to users you should include them here. When an approved claim is moved to your standard report the EPI values will be included. Advertiser information: Some advertisers require extra information on all claims for them to validate them. For example, they may require the user s or postal address used when registering for a service. Enter this information here. Event ID: Tradedoubler use a standard event for transaction inquiries this is event ID 17. Unless you have been instructed otherwise you should use event ID 17. Expected commission: If you are using event ID 17 you must also include the expected commission. If the transaction did not track at all this should be the full commission you expected. If the transaction tracked with the wrong commission this should be the missing amount, not the full amount expected. This must be numerical, must not include any currency symbols and can only use a decimal point (.) as a separator (thousand separators are not required). Proof of claim: It is often useful to include proof of the transaction you are claiming for. You may enter a URL to the proof in this field this could be a scanned copy of the receipt, an confirmation, etc. When you have completed the form click the Create claim button. You will be returned to the Claims tab and will see the new claim set as pending: Tradedoubler s automated quality checks will now take place. If there are any issues the claim status will be set to Validation error and an explanation included. To see this hover over the status symbol:

7 5. Creating multiple claims If you need to create a large number of claims you can use the Upload claims tab: Simply click the Choose file button, select the file and click Upload claim. A status message will be displayed to show if the upload was successful or not. See Appendix A for the claims file specification. 6. Review updated claims If a new claim passes Tradedoubler s quality checks it will be sent to the advertiser for review. They have the following options: 1. Reject the claim A reason must be selected from a pre-defined list. 2. Approve the claim The order value and expected commission may be edited. This may be because part of the order was returned, the entered amount included tax and shipping, etc. Changes to these values will be clearly displayed to you in the adjusted order value and adjusted expected commission columns.

8 A list of all possible statuses (approvals and denials) is included in Appendix B. You can review claim updates on the Claims tab: You can filter to a specific status (e.g. rejected), hover over the status symbol for more information and see if there have been any changes made to order values and expected commissions. 7. Export claims You may wish to export pending or updated claims to review or to import to your own system. You can do this using the Export claims to CSV button:

9 Appendix A Claims file specification You must define the field order in a headers row in your CSV file so that Tradedoubler s importer knows how to handle each field. The order is flexible and can include the following fields: Name Value Mandatory? affiliatesiteid Integer Yes programid Integer Yes timestampevent YYYY-MM-DD Yes ordernumber Alphanumeric Yes ordervalue Float Yes eventid Integer Yes epi Alphanumeric No epi2 Alphanumeric No proofofclaims Text/URL No advertiserinformation Test No expectedcommission Float No trackingurl Text/URL No productname Text No Note: The file MUST use a semi-colon (;) as the separator. It is advisable to use double quote (") as a text qualifier to ensure the integrity of data is retained. If using double quotes you must ensure they are plain text (") and not rich text ( ). The date format must match that described above (YYYY-MM-DD) with no time included. Empty fields should be left completely blank do not use a space or any other identifier (e.g. a missing field when using a text qualifier will look like "")

10 Appendix B Status list All claims will have one of the following status IDs: ID Name State 1 Reported REPORTED 2 Awaiting approval PENDING_ADVERTISER 3 Approved APPROVED 100 CANNOT_VALIDATE PENDING_TRADEDOUBLER 101 Missing parameter REJECTED 102 Program not found REJECTED 103 Program not active REJECTED 104 Tariff not found REJECTED 105 Commission mismatch PENDING_TRADEDOUBLER 106 Already tracked REJECTED 107 Already tracked but pending REJECTED 108 Already tracked but not accepted REJECTED 109 Already tracked for other site REJECTED 110 Already tracked for other site but pending REJECTED 111 Already tracked for other publisher REJECTED 112 Invalid site id REJECTED 113 Site not approved REJECTED 114 Advertiser does not accept claims REJECTED 115 Transaction date in future REJECTED 116 Invalid event type REJECTED 201 Attributed to another marketing channel REJECTED 202 Application/credit check denied REJECTED 204 Fraudulent order/application REJECTED 205 Insufficient information REJECTED 206 Invalid order number REJECTED 207 Order Cancelled or returned REJECTED 208 Transaction cannot be traced REJECTED 209 Transaction not fully completed online REJECTED 210 Voucher/discount code used REJECTED Note: A new claim will be assigned status ID 1 and will pass through Tradedoubler s quality check process. If successful the claim will be assigned claim ID 2 and sent to the advertiser for review. If the claim fails Tradedoubler s quality checks it will be assigned a status ID between 100 and 116. Claims that are sent to the advertiser for review will be assigned a status ID of 3 or between 201 and 210, depending on the advertiser s response.