GovX offers several automated options for reporting transactions and commissions on ticket purchases and travel reservations. You must implement one of the approved tracking methods in order to list your offer on the Govx.com site.
The two preferred integration methods are via a tracking pixel or an HTTP post. The pixel is implemented in the HTML of your application and is used for content management systems where server code is unavailable. The HTTP post method is used in scenarios where it is easier to call from backend services. For implementation guides, please refer to the following:
If you are not able to integrate via either the tracking pixel or the HTTP post methods, we also offer a simple CSV integration, which is covered in this document.
Customer Identifier in Query-string
As part of the implementation, we will place protected links on GovX.com to allow our members to access your offering. When one of these links is clicked, we will append a unique customer identifier using a query-string name/value pair. The default query-string name is "_xcid", but can be modified to meet your specifications.
You will need to parse the query-string to capture the value and transmit it back to GovX when reporting commission.
An example link could look as follows:
Commission reports should be sent to GovX once-per-day at a consistent time using a CSV flat-file format. You have two options for transmitting the files.
- SFTP: We will give you access to a secure FTP server location where you can deposit the files. This is the preferred method for transmitting CSV files.
- Email: We can set up an individual inbox for your account (ex: email@example.com)
The files should contain the transaction details, including the customer identifier. A specific file format will be provided to you by your account manager.