# Real Estate Ads - Get Started
**Note:** For commerce, to publish Real Estate listings, your business needs to be [verified](https://developers.facebook.com/docs/marketplace/realestate/business-verification).
**Step 1: Create a [Home Listing catalog](#create-home-listing-catalog)**.
**Step 2: [Set up listing and pricing](#setup-home-listing-and-pricing)**.
**Step 3: [Update options](#update-options)**.
**Step 4: [Filter listing catalog to listing set](#filter-to-home-listing-set)**.
**Step 5: [Send Offline Conversions](#send-offline-conversions)** (Optional)
**Step 6: Build your [Audience for Real Estate](https://developers.facebook.com/docs/marketing-api/dynamic-ads-for-real-estate/audience)**. Differently from what happens with real estate listings published by users, for partner integrations, leads are sent to partners via lead form, rather than via Messenger chat. Learn more about [Retrieving Leads for commerce](https://developers.facebook.com/docs/marketplace/realestate/leads).
**Step 7: [Create and deliver ads](https://developers.facebook.com/docs/marketing-api/dynamic-ads-for-real-estate/ads-management) for your home listings**.
**Step 8: Get delivery information to see how people on Facebook are engaging with your ads**. See [Ads Insights](https://developers.facebook.com/documentation/ads-commerce/marketing-api/reference/adgroup/insights).
**Step 9: Use debugging tools to diagnose and resolve problems**. See [Advantage+ Catalog Ads Debugging Tools](https://developers.facebook.com/docs/marketing-api/dynamic-product-ads/debugging-tools).
## Step 1: Create a Home Listing Catalog {#create-home-listing-catalog}
### For Advantage+ catalog ads
Your catalog should contain a list of properties that you want to advertise. See [Catalog Reference](https://developers.facebook.com/documentation/ads-commerce/marketing-api/reference/product-catalog).
To create a home listing catalog for Advantage+ catalog ads, set `vertical` to `home_listings`:
### cURL
```
curl \
-F 'name=Home Listing Catalog Name' \
-F 'vertical=home_listings' \
-F 'access_token=<ACCESS TOKEN>' \
https://graph.facebook.com/<API_VERSION>/<BUSINESS_ID>/owned_product_catalogs
```
To use the catalog API, you need [Marketing API Access Level](https://developers.facebook.com/documentation/ads-commerce/marketing-api/get-started/authorization#limits) and accept the [Terms of Service](https://business.facebook.com/legal/product_catalog_terms/) by creating your first catalog through [Business Manager](https://business.facebook.com).
### For commerce
For instructions on how to create a catalog for commerce, visit the [Marketplace Platform documentation](https://developers.facebook.com/docs/marketplace/realestate/uploading-listings#create-a-real-estate-catalog-with-the-product-catalog-ui).
## Step 2: Set Up Listing and Prices {#setup-home-listing-and-pricing}
Your listing contains information for properties, such as listing ID, name, availability, description, address, bedrooms, bathrooms, and so on. You can have a set of listings uploaded or fetched from your business. A listing item is a single property presented on your website or app.
### Supported Feed Formats {#supported-feed-format}
You can have a single feed for all properties in your catalog, or you can have multiple feeds where one feed represents properties in a single country, for a single real estate agency, or for one broker.
**For Advantage+ catalog ads**, you must provide the listing feed in one of these formats:
| File Format | Description | Sample File |
| --- | --- | --- |
| XML | Typically generated by automated feed provider systems. A root `<listings>` XML node encloses a set of `<listing>` nodes, each representing a home listing. The file must begin with a valid `<?xml` declaration tag. | [Download](https://lookaside.facebook.com/developers/resources/?id=dare_home_listing_feed.xml) |
| CSV, TSV | The first row must list the chosen field names in the order the values will be given. Subsequent rows then supply the corresponding values for each home listing. Nested or multi-value fields such as image can be represented using JSON-encoded values or by a set of "flattened" plain-text columns labeled using JSON-path syntax, such as `image[0].url`, `image[0].tag[0]`, `image[0].tag[1]`. | [Download](https://lookaside.facebook.com/developers/resources/?id=dare_home_listing_feed.csv) (CSV) |
**For commerce**, you must provide the listing feed in **XML** format:
| File Format | Description |
| --- | --- |
| XML | Typically generated by automated feed provider systems. A root `<listings>` XML node encloses a set of `<listing>` nodes, each representing a home listing. The file must begin with a valid `<?xml` declaration tag. |
| CSV, TSV, JSON | ***These formats are not currently supported.*** |
Our feed parser automatically detects `UTF8`, `UTF16` or `UTF32` text-encodings, falling back to `LATIN1` if unexpected byte sequences appear.
#### Feed XML example {#feed-xml-example}
```xml
<?xml version="1.0" encoding="UTF-8"?>
<listings>
<title>example.com Feed</title>
<link rel="self" href="http://www.example.com"/>
<listing>
<home_listing_id>12345678</home_listing_id>
<name>1 Hacker Way, Menlo Park, CA 94025</name>
<availability>for_rent</availability>
<description>An amazing listing</description>
<address format="simple">
<component name="addr1">1 Hacker Way</component>
<component name="city">Menlo Park</component>
<component name="region">California</component>
<component name="country">United States</component>
<component name="postal_code">94025</component>
</address>
<latitude>1.11414</latitude>
<longitude>-1.835003</longitude>
<neighborhood>Menlo Oaks</neighborhood>
<image>
<url>http://example.com/12345678-1.jpg</url>
</image>
<image>
<url>http://example.com/12345678-2.jpg</url>
</image>
<image>
<url>http://example.com/12345678-3.jpg</url>
</image>
<listing_type>for_rent_by_agent</listing_type>
<num_baths>6</num_baths>
<num_beds>5</num_beds>
<num_units>1</num_units>
<price>110000 USD</price>
<property_type>house</property_type>
<url>http://www.example.com/link_to_listing</url>
<year_built>2007</year_built>
</listing>
</listings>
```
### Supported Fields - Home Listings {#home-listing-fields}
The following supported fields are designed for items you add to your product catalog. For a complete list of supported fields, see the [Home Listing reference](https://developers.facebook.com/docs/marketing-api/reference/home-listing).
For localized catalogs, see [supported fields for home listings](https://developers.facebook.com/documentation/ads-commerce/catalog/reference#loc-cat-home).
Our feed parser automatically detects `UTF8`, `UTF16` or `UTF32` text-encodings, falling back to `LATIN1` if unexpected byte sequences appear. While text in field values can be given in any language, field names must be given exactly as below, in English.
| Field Name and Type | Description |
| --- | --- |
| `home_listing_id`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Unique home (apartment/condo) listing ID; most granular ID possible.<br><br>Example: `FB_home_1234` |
| `home_listing_group_id`<br><br>type: string | **Not applicable to Advantage+ catalog ads. Optional for commerce.**<br><br>Building or apartment's unique ID. Must be unique per group. |
| `name`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Title of home listing. Example: `Modern Eichler in Green Oaks` |
| `availability `<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Current availability for the home listing. Supported values are: `for_sale`, `for_rent`, `sale_pending`, `recently_sold`, `off_market`, `available_soon`. For commerce, the only supported value is 'for_rent'. |
| `address`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Street address for the property that must be resolvable to its location.<br><br>See [**Address Object Parameters**](#address-object).<br><br>Example: `1 Hacker Way` |
| `address.city`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>City where the property is located.<br><br>See [**Address Object Parameters**](#address-object).<br><br>Example: `Menlo Park` |
| `address.region`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>State, county, region, or province for the property.<br><br>See [**Address Object Parameters**](#address-object).<br><br>Example: `Menlo Park` |
| `address.country`<br><br>type: object | **Required for Advantage+ catalog ads and commerce**.<br><br>Country where the property is located.<br><br>See [**Address Object Parameters**](#address-object).<br><br>Example: `United States` |
| `address.postal_code`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Country where the property is located.<br><br>See [**Address Object Parameters**](#address-object).<br><br>Example: `United States` |
| `latitude`<br><br>type: float | **Required for Advantage+ catalog ads and commerce**.<br><br>Latitude of the listing.<br><br>Example: `37.484100` |
| `longitude`<br><br>type: float | **Required for Advantage+ catalog ads and commerce**.<br><br>Longitude of the listing.<br><br>Example: `-122.148252` |
| `neighborhood`<br><br>type: string | **Required for Advantage+ catalog ads. Optional, but strongly recommended for commerce**.<br><br>Max neighborhoods allowed: 20<br><br>Listing neighborhood for the property. Can have multiple neighborhoods. If you have more than one neighborhood, add additional columns for each type and use JSON-path syntax in each column name to indicate the number of neighborhoods.<br><br>Example: `neighborhood[0]; neighborhood[1]` |
| `price`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Sale or rental price of the property. Format price as the cost, followed by the [3-digit ISO currency code](https://en.wikipedia.org/wiki/ISO_4217), with a space between cost and currency.<br><br>Example: `13,999 USD` |
| `image`<br><br>type: object | **Required for Advantage+ catalog ads and commerce**.<br><br>Maximum images: 20<br><br>Maximum size: 4 MB<br><br>The URL for the image used in your ad.<br><br>* For square (1:1) aspect ratios in the carousel ad format, your image should be 600x600.<br>* For single image ads, your image should be at least 1200x630 pixels.<br>* **For commerce**, The first photo is displayed in the commerce feed as the cover image.<br><br>Example: `image[0].url`, `image[0].tag[0]`<br><br>See [**Image Object Parameters**](#image-object). |
| `url`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Link to the property listing page. Must be a valid URL.<br><br>See [**Image Object Parameters**](#image-object).<br><br>Example: `http://www.realestate.com` |
| `description`<br><br>type: string | **Optional for Advantage+ catalog ads. Required for commerce**.<br><br>Max characters: 5000<br><br>Description of the property.<br><br>Example: `Beautiful 3BD home available in Belmont` |
| `num_beds`<br><br>type: float | **Optional for Advantage+ catalog ads. Required for commerce**.<br><br>Total number of bedrooms. Can be `0` for Studios.<br><br>Example: `2` |
| `num_baths`<br><br>type: float | **Optional for Advantage+ catalog ads**.<br><br>Total number of bathrooms. For commerce, must be `1` at minimum. |
| `num_rooms`<br><br>type: float | **Not applicable for Advantage+ catalog ads. Required for commerce.**<br>Total number of rooms of property. |
| `property_type`<br><br>type: string | **Optional for Advantage+ catalog ads**.<br><br>Type of property. Supported values for Advantage+ catalog ads: `apartment`, `condo`, `house`, `land`, `manufactured`, `other`, `townhouse`. Supported values for commerce: `apartment`, `builder_floor`, `condo`, `house`, `house_in_condominium`, `house_in_villa`, `loft`, `penthouse`, `studio`, `townhouse`, `other`. |
| `listing_type`<br><br>type: string | **Optional for Advantage+ catalog ads**.<br><br>Type of property listing. Supported values for Advantage+ catalog ads: `for_rent_by_agent`, `for_rent_by_owner`, `for_sale_by_agent`, `for_sale_by_owner`, `foreclosed`, `new_construction`, `new_listing`. Supported values for commerce: `for_rent_by_agent`, `for_rent_by_owner`. |
| `area_size`<br><br>type: int | **Not applicable for Advantage+ catalog ads. Required for commerce.**<br><br>Area or space of the floor plan's listing. |
| `area_unit`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Required for commerce.**<br><br>The units (square feet or square meters) of the floor area's value. Supported values: `sq_ft`, `sq_m`. |
| `ac_type`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Type of air conditioning. Supported values: `central`, `other`,`none`. |
| `furnish_type`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Type of furniture available in the property. Supported values: `furnished`, `semi-furnished`,`unfurnished`. |
| `heating_type`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Type of heating installed in the property. Supported values: `central`,`gas`,`electric`,`radiator`,`other`,`none`. |
| `laundry_type`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Type of laundry available. Supported values: `in_unit`,`in_building`, `other`,`none`. |
| `num_units`<br><br>type: int | **Optional for Advantage+ catalog ads and commerce**.<br><br>Total number of units (apartments, condos) available for rent.<br><br>Example: `0` |
| `parking_type`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Type of parking available on property. Supported values: `garage`,`street`,`off-street`, `other`,`none`. |
| `partner_verification`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Whether the partner company has verified the listing. Supported values: `verified`, `none`. |
| `year_built`<br><br>type: string | Year the property was built, using the _YYYY_ format, 4 digit year.<br><br>Example: 1994. |
| `pet_policy`<br><br>type: string | **Not applicable for Advantage+ catalog ads. Optional for commerce.**<br><br>Indicates the pets allowed on the property: `cat`, `dog`, `all`, `none`. |
| `available_dates_price_config`<br><br>type: object | List of dates and prices that a listing is available. When you provide values, Facebook can recommend listings based on their available dates and dynamically show the associated price in your ad.<br><br>See [**Available Dates Object Parameters**](#available_dates-object) |
| `applink`<br><br>type: object | App link to listing. |
| `status`<br><br>Type: string | Controls whether an item is active or archived in your catalog. Only active items can be seen by people in your ads, shops or any other channels. Supported values: `active`, `archived`. Items are active by default. Learn more about [archiving items](https://www.facebook.com/business/help/543317109402043?id=725943027795860).<br><br>Example: `active`<br><br>**Note**: Some partner platforms such as Shopify may sync items to your catalog with a status called **staging**, which behaves the same as `archived`.<br><br>**Warning:** This field was previously called `visibility`. While we still support the old field name, we recommend that you use the new name. |
### Country-Specific Required Fields — Commerce Only {#country_specific}
[Visit the Marketplace Platform documentation for commerce country-specific required fields](https://developers.facebook.com/docs/marketplace/realestate/uploading-listings#country_specific).
### Image Object Parameters {#image-object}
| Field Name and Type | Description |
| --- | --- |
| `url`<br><br>type: string | **Required for Advantage+ catalog ads and commerce**.<br><br>Image source URL. Follow these image specifications:<br><br>* All images must be in JPG, GIF, or PNG format.<br><br>* For carousel ads and collection ads: Images display in square (1:1) format. The minimum image size is 500 x 500 px. We recommend 1024 x 1024 px for best quality.<br><br>* For single image ads: Images display at a 1.91:1 aspect ratio. The minimum image size is 500 x 500 px. We recommend 1200 x 628 px for best quality. |
| `tag`<br><br>type: string | **Optional for Advantage+ catalog ads and commerce**.<br><br>Tag appended to the image that shows what's in the image. There can be multiple tags associated with an image.<br><br>Examples: `Fitness Center`, `Swimming Pool`<br><br>`INSTAGRAM_STANDARD_PREFERRED` - Allows advertisers to tag a specific image in their feed as the default image that will be used for Instagram. This tag is case sensitive. |
### Address Object Parameters {#address-object}
| Field Name and Type | Description |
| --- | --- |
| `addr1`<br><br>type: string | **Required**.<br><br>Street address of hotel.<br><br>Example: `675 El Camino Real` |
| `city`<br><br>type: string | **Required**.<br><br>City where hotel is located.<br><br>Example: `Palo Alto` |
| `region`<br><br>type: string | **Required**.<br><br>State, county, region or province for hotel.<br><br>Example: `California` |
| `country`<br><br>type: string | **Required**.<br><br>Country of the hotel.<br><br>Example: `United States` |
| `postal_code`<br><br>type: string | Postal or zip-code of the property. **Required** unless country does not have a postal-code system.<br><br>Examples: `94125`, `NW1 3FG` |
### Available Dates Price Config {#available_dates-object}
With `available_dates_price_config`, you can provide the availability and prices of each property for a given date range. When you include date ranges in this field, Facebook factors this availability into our product recommendations and tries to show listings that are available for the dates someone searched on your site. Optionally, if you include pricing we can also show date-specific prices in your ad creative. **To enable this feature, you must also send Facebook `lease_start_date` and `lease_end_date` in your [pixel events](https://developers.facebook.com/docs/marketing-api/dynamic-ads-for-real-estate/audience).**
#### Available Dates Object Parameters {#dates-object}
| Field Name and Type | Description |
| --- | --- |
| `start_date`<br><br>type: string | **Optional if `end_date` is provided**.<br><br>Start of the available date range in ISO-8601 format; inclusive of the start date. If you only provide `start_date`, `end_date` defaults to a year from that date.<br><br>Example: `YYYY-MM-DD`, such as `2018-01-01`. |
| `end_date`<br><br>type: string | **Optional if `start_date` is provided**.<br><br>End of the available date range in ISO-8601 format; excludes the end date. If you only provide `end_date`, `start_date` defaults to the current date.<br><br>Example: `YYYY-MM-DD`, such as `2018-02-01`. |
| `rate`<br><br>type: string | Integer price of the listing during this time range.<br><br>Example: `10000` if the listing was `$100.00 USD` |
| `currency`<br><br>type: string | **Required if you provide `rate`.**<br><br>[ISO-4217](https://www.iso.org/iso-4217-currency-codes.html) currency code.<br><br>Example: `USD`, `GBP`, etc. |
| `interval`<br><br>type: string | Length of stay for the specified rate.<br><br>Allowed values are: `nightly`, `weekly`, `monthly`, `sale`. |
This is an example of a listing's availability and how it appears in JSON:
```js
"available_dates_price_config": [
{
// available until 11/01 at $150/night
"end_date": "2018-11-01",
"rate": "15000",
"currency": "USD",
"interval": "nightly",
},
{
// available from 11/01 - 12/01 at $200/night
"start_date": "2018-11-01",
"end_date": "2018-12-01",
"rate": "20000",
"currency": "USD",
"interval": "nightly",
},
{
// available from 11/01 onward at $500/week
"start_date": "2018-11-01",
"rate": "50000",
"currency": "USD",
"interval": "weekly",
},
]
```
### Product deep links
[Provide deep links](https://developers.facebook.com/documentation/ads-commerce/catalog/guides/product-deep-links) in feed following the [App Links](https://developers.facebook.com/docs/applinks) specification. Deep link information in feed takes precedence over any information Facebook collects with App Links metadata with our web crawler.
If you already have deep link information from App Links, you don't need to specify this data. Facebook uses information from App Links to display the correct deep link. To display deep links in your ads, see [Advantage+ Catalog Ads, Ad Template](https://developers.facebook.com/docs/marketing-api/dynamic-product-ads/ads-management#adtemplate).
## Step 3: Update Options {#update-options}
### Advantage+ Catalog Ads
**For Advantage+ catalog ads**, you can refresh home listing info in the catalog through the following ways with direct upload. See [Direct Upload Feed Reference](https://developers.facebook.com/documentation/ads-commerce/marketing-api/reference/product-feed/uploads)
**Example** — You can manually do a one-time upload:
### cURL
```
curl \
-F "url=http://www.example.com/sample_feed.xml" \
-F "access_token=<ACCESS_TOKEN>" \
https://graph.facebook.com/<API_VERSION>/<PRODUCT_FEED_ID>/uploads
```
### Commerce
**For commerce**, you can refresh home listing info in the catalog by setting up a recurring (scheduled) feed upload and updating your feed. In Marketplace, we highly recommend using the Set a Schedule option.
#### Set a Schedule for Your Catalog Data Feed Upload
- Go to [**Commerce Manager**](https://www.facebook.com/products).
- Click **Data Sources**.
- Click **Add Data Source**.
- Click **Use Data Feeds** and click **Next**.
- Click **Set a schedule**.
- Choose how frequently you want Facebook to check your data feed for updates: **Daily**, **Hourly**, and **Weekly**. If you choose **Hourly** or **Weekly** as your frequency, you can also specify when your scheduled upload repeats.
- Enter the direct URL for your feed. You can use URLs that use HTTP, HTTPS, FTP, or SFTP.
Note: The URL should point directly to your data feed file; otherwise, the upload may fail.
- (Optional) Enter the username and password for the data feed provider. This is different from the username and password you use to access your Facebook ad account.
- Enter a name for your data feed.
- Choose the currency type for your data feed. The currency type is used for your data feed if you don't specify it in your data feed file.
- Click **Next.**
- Review your data feed file for any errors. If you're missing any required columns in your file, or there are columns that Facebook doesn't recognize, you can map them to the appropriate columns [**here**](#setup-home-listing-and-pricing). Any columns mapped here are saved for future data feed uploads.
- Click **Next.**
#### Multilanguage Feed Upload
Commerce supports a multilanguage experience. When you add a secondary language feed to a catalog, you can create another feed with the second language from that single catalog. The information on the secondary feeds overrides your default language when the relevant audience sees your listings.
**This feature is applicable only for specific country partners. Please contact your Facebook representative to check availability in your market**.
- Create a catalog with a data feed for your default language and country.
- Create an XML file only with the listing ID (**home_listing_id**) and additional fields that required local language overwrite like name, description or additional fields. To overwrite information, the **home_listing_id** must match the ones in your original catalog data feed.
- Add the additional information feed from the Commerce Manager.
*Add the additional feed from the Commerce Manager
[Add Home Listing Information] - [Add Language Information] *
- Confirm the two data sources within the same catalog.
## Step 4: Filter Listing Catalog to Listing Set {#filter-to-home-listing-set}
This is a group of items in a catalog that you advertise in your Advantage+ catalog ads. Each listing catalog can have many listing sets.
### cURL
```
curl \
-F "name=test set" \
-F 'filter={"availability":{"eq":"for_sale"}}' \
-F "access_token=" \
https://graph.facebook.com/<API_VERSION>/<CATALOG_ID>/product_sets
```
The above `filter` is made up of the following operators and data:
| Operators | Type of filter |
| --- | --- |
| `i_contains` | Contains substring (case insensitive) |
| `i_not_contains` | Does not contain substring (case insensitive) |
| `contains` | Contains substring (case sensitive) |
| `not_contains` | Does not contain substring (case sensitive) |
| `eq` | Equal to (case insensitive) |
| `neq` | Not equal to (case insensitive) |
| `lt` | Less than (numeric fields only) |
| `lte` | Less than or equal to (numeric fields only) |
| `gt` | Greater than (numeric fields only) |
| `gte` | Greater than or equal to (numeric fields only) |
| Data | Data to filter |
| --- | --- |
| `availability` | Listing availability. Example: `for_sale` |
| `listing_type` | Listing type. Example: `for_sale_by_agent` |
| `property_type` | Property type. Example: `house` |
| `price` | Listing price |
| `name` | Name |
| `city` | City |
| `country` | Country |
| `region` | Region or state |
| `postal_code` | Postal code |
| `num_beds` | Number of beds |
| `num_baths` | Number of baths |
## Step 5: Send Offline Conversions {#send-offline-conversions}
You can send offline conversion events and see how many customers viewed or clicked on Facebook ads and commerce listings before converting; use the [Offline Conversions API](https://developers.facebook.com/documentation/ads-commerce/conversions-api/offline-events) and add the following fields in [step **4. Upload Offline Events**](https://developers.facebook.com/documentation/ads-commerce/conversions-api/offline-events#requirements).
### Match Keys
Match keys compare a conversion to a user.
| Key | Description |
| --- | --- |
| `email` | Email address(es) **Hash** |
| `phone` | Phone number(s) **Hash** |
| `fn` | First name **Hash** |
| `ln` | Last name **Hash** |
| `madid` | Apple or Android advertising ID **Hash** |
| `zip` | ZIP code(s) **Hash** |
| `ct` | City **Hash** |
| `st` | State **Hash** |
| `country` | Country **Hash** |
| `dob` | Date of birth (DD format) **Hash** |
| `doby` | Date of birth (YYYY format) **Hash** |
| `gen` | Gender **Hash** |
| `age` | Age **Hash** |
| `lead_id` | Lead ID of Marketplace leads |
### Custom Data
Custom data compares a conversion to a dealer.
| Field | Description |
| --- | --- |
| `content_ids` | `home_listing_id` from the catalog upload |
| `content_type` | Set to `home_listing` |
### Event Details
Event details describe the offline conversion event that took place.
The upload frequency is daily, within 48 hours of the event.
| Field | Description |
| --- | --- |
| `event_name` | **Required**<br><br>Event type enum:<br><br>`ViewContent`<br><br>`Search`<br><br>`AddToCart`<br><br>`AddToWishlist`<br><br>`Lead` = Had a phone call or other qualified lead<br><br>`CompleteRegistration` = Appointment setup<br><br>`InitiateCheckout` = Agency visit<br><br>`AddPaymentInfo` = Property viewing<br><br>`Purchase` = Lease signed<br><br>`Other` |
| `event_time` | **Required**<br><br>Time of the event |
| `value` | **Required**<br><br>Rent value. Set to `0` for non-lease events. |
| `currency` | **Required**<br><br>Currency code |