Link Attribution
Booking attribution for the Android 3.x integration.
The SDK builds booking links using the partner ID (aid) supplied during initialization. You do not need to construct these links for a normal integration. Set Stay22.campaignId before submitting the trip when you want campaign segmentation.
Sending your own notification
If your app owns its notification engine, link to https://www.stay22.com/allez/roam with the destination, optional dates, and your Stay22 partner ID:
https://www.stay22.com/allez/roam?address=Lisbon%2C+PT&checkin=2027-03-14&checkout=2027-03-18&aid=your-partner-id&source=direct&medium=pushnotif_manualCopy the URL as one line. Use medium=pushnotif_manual to distinguish your sends from SDK sends. Leave off the SDK-only product and request-tracking fields. Destination text uses address or hotelname; coordinates use both lat and lng. Dates use YYYY-MM-DD. Optional adults, children and campaign further describe the trip.
About sid22
Stay22 issues sid22; the SDK stores it and reuses it for links and events. Do not generate one yourself. If your own notification engine has no Stay22 session identifier, omit it. The partner ID still provides booking attribution, while the missing session identifier prevents connecting that click to the SDK session's earlier events.
When sending your own notification, your app owns consent, timing, replacement, cancellation and frequency caps. See the SDK integration if you want the SDK to handle those functions. Contact support@stay22.com to confirm your attribution setup.