> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/integrations/email-marketing/snippets/post-stay-email.md).
# Post-stay email
**Add a banner to your post-stay email to invite guests to share their stories about their stay.**
A dynamically generated, linked image can be added to your email template that is unique for each guest and can be easily tweaked from your Flip.to account, including size, messaging and styling.
{% hint style="info" %}
The banner can easily be toggled on or off from your account. If it is turned off, the image will not be displayed and a transparent 1x1 pixel will be served in its place.
{% endhint %}
## Banner code snippet
The basic structure of the snippet to be added is:
```html
```
| |
|---|
| LinkURL | Points guests to their story submission page: https://flip.to/property/poststay/email/link |
| ImageURL | Loads the image asset that invites guests to submit their story: https://flip.to/property/poststay/email/image |
| ImageDescription | Makes sure your image is screen-reader friendly and compliant with the Americans with Disabilities Act (ADA). Add in the alt attribute directly in the tag. We suggest the following alt text for the post-stay email image: alt=”We'd love to hear about a favorite moment from your stay. You can also join fellow guests and enter your story in our story contest!”
|
{% code title="Sample" overflow="wrap" %}
```html
```
{% endcode %}
### Parameters
Below are the parameters that should be appended to both the **LinkUrl** and **ImageUrl**. All values should be properly URL encoded.
| Name | Value | Description |
| ----------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| companyCode | Your Flip.to company
code
| Please check with your [Customer Success Manager](/docs/support/customer-success.md) if needed and replace `XX` with your own companyCode. |
| code | The property code used by your booking engine | Replace `YY` with your own property booking engine code. |
| crsnumber | The reservation CRS number,
if available
| |
| pmsnumber | The reservation PMS number, if available. | |
| loyalty | Guest's loyalty program number, if any | |
| first | Guest's first name | |
| last | Guest's last name | |
| email | Guest's email address | In cases that there may be more than one possible email available, this can be populated with a pipe ( |
| startDate | Guest’s check-in date | Dates should be formatted as yyyy-M-d
For example: 2028-5-15 or 2028-05-15
|
| endDate | Guest’s check-out date | If this is not available please see the nights parameter under advanced configuration below. |
| type | The guest’s room type, if available | This should include the booking engine internal code, and not the room type description. |
| rateCode | The guest’s rate code, if available | |
| groupCode | The guest’s group code (or block code), if available | |
| promoCode | The guest’s promo code, if available | |
| language | The language ANSI code the guest has used to make the reservation | For English use en, French fr, etc. Here’s a complete list of ISO 639-1 language codes
Optionally a culture name can be used as well. For example this can be set to en-US or en\_US.
|
| currency | The 3 character currency code the guest has used to made the purchase | Here's a [complete list of currency codes](https://www.xe.com/currency/). For instance USD for US Dollars. |
| amount | The total amount used for the purchase based on the defined currency | Amount should be supplied as a valid number including a decimal point if appropriate. |
### Advanced Configuration
| Name | Value | Description |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| nights | Optional
The number of nights that the guest has stayed at the hotel. This should be set as a number.
| If `endDate` is not available, this field can be set to the actual or estimated (i.e. the average night stay) length of guest stay. |
| dateFormat | Optional
Specifies a different date format for the startDate and endDate parameters.
| By default dates should be specified as yyyy-M-d. However, you can change the default format by entering the appropriate format here.
For example, if dates are entered as 12/31/2028 the date format to be specified is M/d/yyyy.
|
| mobile | Optional
Setting to true indicates that the mobile version of the image should be displayed. Default is a desktop image.
| This is only supported for the **ImageURL.** |
| overrideImageUrl | Optional
Overrides the default image with a custom image.
| When using custom images, one should use the https protocol, and might want to create a unique image per language. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.flip.to/docs/integrations/email-marketing/snippets/post-stay-email.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.