U-ON.Travel report: bookings, payments, margin

Travel agency reporting on U-ON.Travel data

A travel agency sells an expensive, infrequent product. Weeks pass between the first question about a May beach holiday and a paid tour, and many leads end in refusal. Advertising is seasonal, and at peak time the owner needs to know which channel brings travellers who book rather than just ask. U-ON.Travel keeps the whole path: lead, booking with a price calculation, status, refusal reason and payments. Reportkey reads this through the API and turns it into a section of a recurring report.

Connecting U-ON.Travel with an API key

The key is created inside U-ON under Settings, Integrations, API. The report needs GET API enabled, which means read access with no right to create or edit bookings. The vendor advises binding the key to the service’s IP addresses, and Reportkey addresses go into that same setting.

You enter the key once on the integrations page, where it becomes a shared connection. An agency serving several tour companies adds one key per company and selects the right one in each project. If the key is reissued, the connection is flagged for re-authorisation and project settings stay intact.

Lead analytics by source for travel agencies

The first block answers the marketer’s question of where travellers come from. Leads are selected by creation date and bookings by creation or closing date. The U-ON booking card keeps the source and the full UTM set, so the block can group by the source list or by campaign:

• Leads received in the period;
• Bookings the manager started to build;
• Lead-to-booking conversion;
• Breakdowns by source, UTM campaign, manager, office and period.

When a website form does not pass a tag, the booking lands in a no-source row, a useful signal of how well data flows from the site.

Closed bookings and refusal reasons

The second block shows sales results. Closed bookings and refusals come from status, and U-ON stores a refusal reason from the agency’s own list. A monthly reason summary says more than any single booking: if half the refusals cite price, the problem is not the ads. Tour value for closed bookings sits alongside, split by office and destination.

Traveller payments, currency and rate

U-ON payments can be income or expense, from clients or to partners, in several currencies. Each one stores its rate, and the report converts with that rate. Traveller payments and tour operator payments appear separately.

Agency margin per booking

A booking calculation holds the client price and the net cost owed to the tour operator; the difference is agency margin. Its accuracy depends on managers filling in net cost, otherwise margin looks inflated. The report shows margin by period and source.

Travel agency CRM and ads in one document

U-ON data usually sits next to Yandex Direct campaigns, VK Ads, CoMagic or Calltouch calls and site traffic in Yandex Metrica. See the context agency demo report, other niche systems on the CRM integrations page, and the free trial on pricing.