--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/quora-actions#article headline: Quora Conversions API description: Connect the Quora Conversions API destination to Segment to send server-side data to Quora. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/quora-actions inLanguage: en dateModified: 2026-09-07T11:23:09.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Quora Conversions API ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Quora Conversions API** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Quora](https://business.quora.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) puts your brand in front of a global audience actively searching for answers across millions of topics, reaching people at the exact moment they're most open to new information. Advertisers use Quora to drive awareness and consideration among highly engaged, high-intent users, with targeting built around what people are actually asking and researching. This destination is maintained by Quora. For any issues with the destination, [contact the Quora support team](mailto:ad-support@quora.com). ## Getting started 1. From your workspace's [destination catalog](https://app.segment.com/goto-my-workspace/destinations/catalog), search for **Quora Conversions API**. 2. Select **Quora Conversions API** and click **Add Destination**. 3. Select an existing source to connect to **Quora Conversions API**. 4. In [Quora Ads Manager](https://www.quora.com/ads), open the **Conversion API** tab and click **Generate Token** to create your **API token**. Your **Account ID** is your Quora ad account ID, shown in the Ads Manager URL as `id=`. 5. Paste the **API token** and **Account ID** in the Quora Conversions API destination settings in Segment. ## Destination Settings | Field | Description | Required | Type | | ---------- | ------------------------------------------------------------------------------------------------- | -------- | -------- | | Account ID | Your Quora ad account ID. Conversion data is attributed to this account. | Yes | string | | API Token | The Conversion API token generated for your account in Quora Ads Manager. Sent as a Bearer token. | Yes | password | ## Available Presets Quora Conversions API has the following presets | Preset Name | Trigger | Default Action | | --------------------- | ------------------------------------------------------------ | --------------- | | Add to Cart | Event type = "track" and event = "Product Added" | Send Conversion | | App Install | Event type = "track" and event = "Application Installed" | Send Conversion | | Add Payment Info | Event type = "track" and event = "Payment Info Entered" | Send Conversion | | Initiate Checkout | Event type = "track" and event = "Checkout Started" | Send Conversion | | Add to Wishlist | Event type = "track" and event = "Product Added to Wishlist" | Send Conversion | | Purchase | Event type = "track" and event = "Order Completed" | Send Conversion | | Search | Event type = "track" and event = "Products Searched" | Send Conversion | | Complete Registration | Event type = "track" and event = "Signed Up" | Send Conversion | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Quora Conversions API-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Send Conversion](#send-conversion-1) ### Send Conversion Send a conversion event to Quora. Supports all standard Quora conversion types, plus Generic pass-through of the Segment event name. Send Conversion is a **Cloud** action. The default Trigger is `type = "track"` | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------- | | Event Name | The conversion event name sent to Quora. | Yes | STRING | | Event Timestamp | The time the conversion occurred. Sent to Quora as epoch microseconds. | No | DATETIME | | Click ID (qclid) | The Quora click ID (\`qclid\`), used to attribute the conversion to a specific ad click. Required by Quora for attribution. | No | STRING | | Value | The monetary value associated with the conversion, in your account currency. Sent to Quora as a number, for example \`99.99\`. Do not include currency symbols or codes. | No | NUMBER | | Event ID | A unique identifier for the event, used to deduplicate events sent via both the Conversions API and the Quora pixel. | No | STRING | | User | User identifiers and attributes. Sent to Quora as plaintext (not hashed). | No | OBJECT | | Device | Device identifiers and attributes. | No | OBJECT | | Batch Data | When enabled, Segment sends events to Quora in batches. | No | BOOLEAN | ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.