Send your event data from RudderStack to Quora Pixel.
5 minute read
Quora Conversion Pixel is a popular advertising and marketing tool to track your website traffic and conversions. If you are running ad campaigns on Quora, you can attribute the downstream user actions on your website to your Quora impressions.
In the web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the Quora Pixel native SDK from thehttps://a.quora.com/ domain.
Based on your website’s content security policy, you might need to allowlist this domain to load the Quora Pixel SDK successfully.
Get started
Once you have confirmed that the source platform supports sending events to Quora Pixel, follow these steps:
From your RudderStack dashboard, add the source. Then, from the list of destinations, select Quora Pixel.
Assign a name to your destination and click Continue.
Connection settings
To successfully configure Quora Pixel as a destination, you need to configure the following settings:
Pixel ID: Enter the Pixel ID from your Quora Ads Manager Account. For more information on getting your Pixel ID, refer to the FAQ section below.
Map RudderStack events to Quora Pixel events: Use this setting to map your events to specific Quora Pixel events.
You can map multiple Quora Pixel events to a single RudderStack event and vice versa. If you do not specify a mapping for a particular event, RudderStack maps it to Quora’s Generic event.
Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to Quora Pixel. For more information on this setting, refer to the Client-side Events Filtering guide.
Use device mode to send events: As this is a web device mode-only destination, this setting is enabled by default and cannot be disabled.
Consent management settings: Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature.
Supported calls
Quora Pixel does not accept the standard RudderStack events, that is, identify, page, etc. directly. You need to first map these event names to the corresponding Quora events in the RudderStack dashboard.
Suppose you specify the following mapping in the RudderStack dashboard:
RudderStack then takes the event name Product Viewed and maps it to Quora’s Search event.
A sample Product Viewed event is shown below:
rudderanalytics.track("Product Viewed");
You can only pass the event name to Quora Pixel. It does not accept any event properties.
RudderStack sends any event for which the mapping is not specified in the dashboard as a Generic event.
Event mapping
Quora Ads supports two types of events, Standard and Custom.
Standard events
Quora Pixel natively supports the following standard events:
Standard event
Description
Generic
Used to track generic actions that are not accounted for in the other categories.
Purchase
Used to track purchases of digital or physical goods.
Generate Lead
Used to track the lead generation process.
Complete Registration
Used to track user signups for a newsletter or service.
Add Payment Info
Used to track the linking of payment information to a user’s account.
Add to Cart
Used to track the addition of items to a cart.
Add to Wishlist
Used to track the addition of items to a wishlist.
Initiate Checkout
Used to track the checkout process initialization.
Search
Used to track different types of searches.
You can map these events to the RudderStack events via the Map RudderStack events to Quora Pixel events dashboard setting.
Custom events
Before you map your RudderStack events to Quora’s custom events, make sure you have first configured the custom event in your Quora Ads Manager account.
To add a new custom event in Quora Ads Manager, follow these steps:
Navigate to the Pixel & events tab in your Quora Dashboard.
Click the Create event button to open the Create custom event modal.
Custom events require a name and description, and category. They also require at least one URL rule in the URL Event setting:
Click Create event to add a new custom event.
By default, Quora Pixel automatically tracks the custom events based on the URL Event setting. You need to include the specific web page URL keywords from which requests will be sent to Quora.
You can also send a specific RudderStack event as a Quora custom event by choosing the Custom event option from the dropdown:
If you send a standard event from a URL that is included in the URL Event property of your custom event configured in Quora Pixel, the event will be recorded in Quora as both a standard and custom event.
FAQ
How do I retrieve the Quora Pixel ID?
To retrieve your Pixel ID from the Quora Ads dashboard, follow these steps:
Navigate to the Pixel & events tab in your Quora Ads dashboard.
Click the Setup Pixel button to open the Install the Quora Pixel modal.
Select Install manually and click the Next button.
In the Step 1: Install the base Pixel modal, copy the installation JavaScript snippet and paste it somewhere safe.
Search for init in the snippet. The string corresponding to init is your Pixel ID. For example, if your snippet contains the following code:
qp('init', 'd2bnp3ubi9x6zq1p89h5hyx2hf5q1k3v');
In this case, d2bnp3ubi9x6zq1p89h5hyx2hf5q1k3v is your Pixel ID.
Can I use the client-side events filtering feature for the custom events?
The client-side events filtering feature is not applicable for custom events. This is because Quora tracks custom events based on the URL Event property.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.