AI Pixel Training / Offline Conversions

Step 1 – Inside Hyros

Please note that this video does not include our recent update, which allows you to send events as orders rather than individual products purchased.

If you want to optimize around orders please send events as a general action and toggle this on:

Step 2 – Inside Google

Written Guide:

To use activate Google offline conversion tracking and AI training

1. Go to your Google ads integrations tab HERE
2. If you are integrated with Google simply flip the offline conversion tracking toggle at the top of the page.
3. Adjust the attribution mode depending on your business type as described in first video. If using scientific mode, adjust the attribution range depending on the average amount of time it takes for your customer to make a sale after clicking an ad.
4. Click “configure” on your integrated google ad account. If you have more than one, you will need to do this for each ad account.
5. Choose how you want to send conversions. By default, Hyros sends a conversion to google depending on the product name (individual action). This can cause issues if you have a lot of different products. Toggle on “Send conversions as a general action” if you want a single general conversion to be sent into google to optimise around instead. Name it whatever you like:

THEN from within your Google ads dashboard:

1. Wait for a sale to come into HYROS
2. Once it has an offline conversion named after it will be created in your Google conversions area, plus the general conversion action will also be created if you have toggled this on.
3. Go to your campaigns that sell this product and set the conversion goal to the HYROS conversion that was just added in the conversion area.

WARNING: If you choose the account level “include in conversions” settings, this may factor in extra conversions and affect campaign performance.
If you do not have the option to select specific conversion actions for the campaign as shown in the above screenshot, please see the video guide above to create a custom goal first.

4. Go into your account settings and ensure that the following field is on inside the Auto-tagging section:

That’s it! You are now AI pixel training with Google. Your ad campaigns will now optimize according to the conversion data that HYROS sends into Google.

If you wish to view the conversions being sent into your google ads account, you can do so inside your google integration settings. Just select “configure” and then you will find you sent conversions under the offline conversions tab:

Events from Hyros are sent to Google on average within 6 hours, they are not able to be sent in real-time due to requirements set by google.

Also, please note that the conversions inside your google account will be attached to your ads, you will NOT be able to view these conversions attached to your videos for example.

Include/Exclude organic sources as offline conversions

By default, we will ignore organic sources when attributing events for the purposes of sending events to Google. If you want to include organic sources, so events are NOT sent when attributed to an organic source, you can toggle this off inside your TT settings:

Sending Leads To Google

Please note you can also send lead events to Google to use for optimization, just turn on lead events inside “general configuration”:

PLEASE READ FIRST: It is only possible for Hyros to send events to conversion actions with an “import” source. If your existing conversion action is not imported, then you must follow the standard setup events instead.
You can check if your conversion action is an imported conversion source by checking the “conversion source” column here:

In this example, only the second conversion action that has a conversion source of “website (import from clicks)” will be able to receive events from Hyros. If your existing event has a conversion source that is not an import source then please follow the standard setup above.

Copy this snippet: Math.random().toString(36).substr(2, 15)

Then paste it with a space in front of 'transaction_id':, and a comma at the end. It should look something like this:

Please read the written guide very carefully before setting this up. We also highly suggest reaching out to the support team to assist with the setup and ensure this is the right setup for you before moving forward.
You are responsible for any sudden changes made that may damage your optimization in Google.

What is an “Existing Google Conversion Action”?

This refers to the events that Google are tracking already, most likely by the Google snippet/pixel added to your site. These are not the same as the events tracked inside of Hyros.

Sending Hyros events to an existing event, will in the case of the example above, send all events to “Google Conversion” Instead of sending Hyros events to a seperate conversion action.

If you have not been tracking events with Google prior to this, you can ignore this section and just follow the main Google guide above.

Why Send Events to An Existing Google Conversion Action? How Does it Work?

It is highly likely you already using these existing events as your conversion goal for optimization purposes for your existing campaigns.

If you are, then sending Hyros events to an existing Google event may be advantageous (we will explain why shortly).

This is especially true if you are using account default goals.

To understand if you are using account default goals: Start by checking if the Google event is set to “Primary” under the action optimization Column, and the “Purchases” conversion goal has the text “Account Default Goal” as shown in the screenshot below.

You should also see the number of campaigns just next to that using the account default goals you have set:

If you want to see if any specific campaigns are using account default goals, you can click edit on any campaign in your ad manager and select “update conversion goals”:

If the Google events are included in these account level goals that you are using, or you are using campaign specific goal settings with Google events, sending our data directly to these Google events will allow you to immediately use Hyros events in optimization without making any other changes.

Should everything work correctly, Hyros events will essentially “fill in the gaps” of the events Google miss, and any events that Google have already tracked correctly will simply be removed by Google to avoid duplication.

For example, let’s say you have an existing conversion action tracked by Google named “Google Conversion”, which is being used as a primary action, and is being used as an account default goal for all your campaigns, Meaning it is already being used in optimization.

If Google track 5 sales for this event, But Hyros track 7, when we send the events to the existing “Google Conversion” event, Google will simply discard the 5 events they already tracked, but keep the 2 events and add them to “Google Conversion”, allowing you to optimize around more accurate data.

If you sent these 7 Hyros events to a seperate “Hyros Conversion” event, then you would not be able to simply use the “Hyros Conversion” event as an account default goal. This is because if you are already using Google events as an account default goal, doing this with Hyros events at the same time would mean optimizing around duplicated events, which could damage your optimization. Google will not deduplicate events if they are in different conversion actions.

This is why by default all seperate Hyros events should be sent in as a “secondary” action and therefore not used in optimization:

The only way to optimize around seperate Hyros events without duplication, is to optimize your campaigns using campaign specific goals, using Hyros events only. See the main Google guide above for more information on that.

This is not necessarily a bad thing, and may even work better for certain businesses. However it can take longer to test and prove better performance before seeing results. This because you then have to switch optimization to a brand new event with no previous data, so you are starting from scratch.

If you send Hyros events to an existing event instead, this means you are optimizing around Hyros events straight away, by using Hyros events to fill in the gaps of the data Google failed to track. That way you maintain using all of the historical data you have gathered and do not have to start from scratch.

Disadvantages and Risks of Sending Hyros Data to an Existing Event

There may be a few reasons why this may not be the best option for you and your businesses, depending on a few different factors:

1. Higher risk of duplication and damage to optimization – Because you are sending data to an existing event, something may go wrong for a number of different reasons.For example, if there could be an error in the setup. Even if there is no setup error there could be a technical issue inside Hyros or even inside Google that prevents Google from deduplicating events correctly, which can lead to damage to your optimization and therefore performance.Because all events are being sent to the same conversion action in Google, if there are any errors you will not be able to easily correct them.Please note by sending events this way, you assume all responsibility for the risks involved. If you are not comfortable with these risks we highly suggest using the standard setup to send events to a unique conversion action instead.
2. Sudden change to account wide optimization in Google – Because the Google conversion action is most likely being used for the majority of your optimization already, suddenly sending the events from Hyros to the same conversion action will likely mean a very sudden change to the numbers that Google are using for optimization across your account.Although the majority of the time, this will be a good thing because Hyros events are just filling in the gaps of missing tracking, this sudden change carries a risk of negatively effecting performance for a temporary period of time during a “buffer” period inside Google.If you are not comfortable with this risk, please just follow the main guide and send events to a unique conversion action. That way you will have more flexibility to test events and change optimization slowly inside Google, one campaign at a time, to avoid sudden changes.
3. Does not necessarily perform better in the long term – Although sending Hyros events to an existing conversion action allows you to improve performance more quickly whilst also utilizing the historical data you have gathered from Google’s tracking, it does not necessarily guarantee that optimization will be performing best this way vs sending Hyros events to a unique conversion action and optimizing for Hyros events on their own, at least in the long term.Each business is unique, and although sending Hyros events this way may give you a boost in performance, optimizing around separate Hyros events may work even better for your business over time.
4. Setup can be more complicated, especially without any coding experience – This requires some editing of the Google pixel code, which may not even be possible for certain businesses. Even if it is possible it can be quite complex without coding experience, and mistakes can have a negative impact on your ad performance.

Add a randomized transaction ID to the Google Snippet – Written Guide

Please follow all of the steps in the main video guide, this is just a more detailed written guide regarding editing the Google Code to add the transaction ID in case you need further assistance setting this up.

This is what allows Hyros to collect the event information to help Google deduplicate the same events they have already tracked.

To do this, you must have access to the pixel/snippet/Gtag code which is used by Google to track the conversion events, and be able to make manual edits to this code. In some cases, you may not be able to do this, such as if you are directly integrating Google Analytics with your landing page software.

If that is the case you can NOT send events this way because you will be duplicating events, so please ignore this section and follow the standard Google guide.

Most commonly, it will be easiest to make edits to Google’s purchase event if you are adding Google’s code manually. Please see their documentation HERE for more information on adding purchase event tracking for Google as an example.

When you have found the event code, copy this snippet: Math.random().toString(36).substr(2, 15)

Then paste it in front of 'transaction_id':, it should look something like this:

Then add this code to the html of the page you are tracking the conversion on. This will most likely be on the thank you page or any page after the lead checks out.

Please also make sure that the same page is being tracked by our universal script, otherwise this will not work.

And this concludes the setup. If you have any questions please reach out to the support team.

Conversion Rules are a great way to customize where you send events to and what is and is not sent based on pre-set conditions. Although there are plenty of other creative ways you can use this, in this guide we will cover some of the most common ways of using this feature, such as:

• Blocking Recurring Sales.
• Blocking free trial events or sending free trial events to a separate conversion action.
• Splitting up sale events depending on which store sales were generated from.
• Sending qualified leads only.
• Blocking Unqualified Calls.
• Sending a product or group of products to a unique conversion action.

To add any conversion rules, go to your Google integration settings and select “configure” on the account you would like to set up conversion rules for:

Then you will have a selection of tabs based on what type of conversion rule you would like to create. If you want to adjust how sales are sent to Google, you will need to add a “sale rule”, for adjusting call events, you will need to add a “call rule” and so on:

Rules can be prioritized, and if no events meet the criteria of any custom rule, the event will be sent to Google using the default settings set in your google integration.

Please find exactly what you are trying to do from the below examples and follow steps:

Checking the status for each conversion sent from hyros

In this case, first please take in mind that Google may be showing different stats for a number of reasons, and once we send events to Google we have no control over how these events are shown by Google. Please see this guide for more details from Google as to why attribution may seem different.

Sending data back to Google is not for the purposes of making decisions with Google data, but for optimization ONLY. For making decisions based on your accurate data we highly suggest using the Hyros chrome extension or the data from inside the app.

The one thing we can control is if we are sending events from Hyros correctly, so before concluding that the issue is on Google’s end, we need to first identify that we are sending the correct data from the Hyros side.

To do this, view the sent conversions inside hyros in the “sent conversions” tab as shown at the top of this section. You should also go to the sales tab or when deep diving into specific sales inside the reports to view the “status” column for each sale as shown here:

If you want to examine larger amounts of data at once, inside a report just load a list of sales by clicking on “sales details” here:

Or alternatively you can even deep dive into a specific group of sales attributed back to a certain source by clicking the “sales” number here on the source row in your report:

Either way, when deep diving into the sales you will see a “created conversions” number here:

If you click on “created conversions” you will get a breakdown of how many sales were sent, how many were not sent and what errors are occurring and how often.

They may have different explanations as to why events weren’t sent, please note below some examples of errors we may receive from Google:

WBRAID_PARAM_FOUND: By default all events with the WBRAID parameters are sent back to your Ad account. If you get the status that the event was not sent because of the WBRAID parameter, it means that your ad account is not on the allowed list. To be whitelisted, contact your Google representative.

INVALID_CLICK: If the click does not exist in Google, then the conversion will not be sent.

UNPARSEABLE_GCLID: The “Gclid” parameter in the URL of the click is invalid, this is requirement from Google that this parameter is attached correctly. This is their parameter, so please be careful not to confuse this with “gc_id” which belongs to Hyros.

EXPIRED_CLICK: If the attributing click was more than 90 days ago, then the conversion will not be sent.

CLICK_MISSING_LABEL: The conversion wasn’t sent because clicks occurred when none of the effective conversion types in the account were enabled could be processed.

GRAPH_METHOD_ERROR: Caused by missing permissions, please ensure you have full admin access to the account, also ensure the same account has access to the pixel, and re-integrate with Facebook inside Hyros to ensure all permissions are granted

EVENT_TIME_TOO_OLD: If the event occured 7 days ago or more, the event can not be sent.

IGNORED: The event was ignored due to a conversion rule set inside your account. If you believe it should have been sent you will need to adjust the conversion rules inside your integration.

DELETED_INTEGRATION: The conversion belongs to an integration that has since been deleted in your account. Please ensure your Facebook integration is set up correctly that inlcude the correct ad account.

CONVERSION_DISABLED: Offline conversions are disabled in the account, when you are ready and ads are tracking correctly please turn this on following the guides above.

NO_FB_GOOGLE_ATTR: We will only send sales that are attributed to Facebook or Google ads. If the sale is not attributed back to a Facebook or Google ad, it will not be sent to the ad platform.

NO_ADSPEND_CLICK_ID: There is no fbclid/gclid in URL of the attributing click. If you investigate the clicks of the lead associated with the sale you should be able to see this as well. These parameters belong to Facebook/Google, and are required for the conversion to be sent. These should not be confused with our tracking parameters, “fbc_id” and “gc_id”.

NO_CLICK_ID: The click ID (associated with fbc_id) was not found inside of Facebook. Please reach out to Facebook for further assistance.

DEFAULT_ERROR: A miscellaneous error. Please retry the sending the conversion in “sent conversions” and if this does not work please reach out to support.

NO_INFO: A similar miscellaneous error. There is no information on the conversion so it can not be sent. Please retry and if this does not work then please reach out to the support team.

How to send failed/pending conversions back to your Ad account if you see the error “Google conversion action does not exist”

If you see this error, there are 2 things you can try:

1) Re-add any deleted conversion actions.

Sometimes this error occurs because a Hyros conversion action previously created inside Google was removed, and Google are not able to create a brand new event on their end.

A common fix for this is to re-add your previous conversion action inside Google.

To do this, click on “view all conversions” and then select the previous conversion actions from Hyros events, and select “enable” as shown:

2) Create a brand new conversion action inside Google

If you have not removed any conversion actions manually, occasionally Google may have an error generating the conversion action automatically.

In this case you will need to manually generate the conversion action in the account before you are able to receive events.

In your Google Ads account, go to Tools & Settings, search for Measurement and click on Conversions. Then click the New conversion action button

The next step you need to click Import and select Other data sources or CRMs-> Track Conversions from clicks:

Here you need to configure the following entries, make sure the conversion name is exactly the same as the event you are sending (ask the Hyros support team if you are not sure about this):

• Goal and action optimization: Select default conversion Purchase
• Conversion name: The conversion name should match the conversion name you have inside Hyros (Offline conversions settings)
• Value: select “Use the same value for each conversion” and then set the currency and the value for this specific conversion. For general conversion actions you will need to select “Use different values for each conversion”.
• Count: here you need to select “Every”.
• Click-through conversion window
• Attribution model.

What information is sent to Google?

Among other things, the main parameters sent to Google are:

• Value.
• Email.
• Phone number.
• Order ID.

Events not being sent due to no click ID being found

The “Click ID” is often seen as the “gclid” or “wbraid” and “gbraid” utm parameters that are added on the landing page URL by Google when a lead clicks on a Google ad.

They should look something like this inside of Hyros when checking a lead’s click history:

Be careful not to confuse this with the Hyros tracking parameters. This click ID is not related to Hyros and comes directly from Google. We have no control over how these are sent with the URL on our end.

This is important because Google requires a “click ID” in order for Hyros to send events to Google for optimization. If there is no click ID then the event will not be sent.

If you notice that the event has not been sent to Google when it should have been, first check the click history of the lead and find the attributing click of the event (if you are sending events using last click mode, then find the click which created the last @source tag).

There can be 2 possible issues related to the click ID:

1. There is no click ID present at all in the attributing click.

If you see the Hyros tracking parameters indicating that this is a google ad click, but the click ID is not present at all (meaning you don’t see “gclid”, “wbraid” or “gbraid” in the URL) then we can not send the event because Google have not been able to pass on the click ID.

Although there’s no way to guarantee Google will send this 100% of the time, there are 2 things we can check to help minimize this from happening:

1. Make sure your ads have no redirects – redirects on ads generally are bad practice when it comes to tracking, and can actually drop utm parameters. This includes Google’s click ID.
2. Check that “auto-tagging” is turned on inside your Google account settings as shown below:
   

2. Click ID is attached, but as “WBRAID” or “GBRAID” instead of “gclid”

The “gclid” utm is the most common way Google add the click ID to the landing page URL after an ad click,

We have done everything on our end to be able to send events to Google in these cases, however, there is still an extra step required for this to be possible. Google need to allowlist your Google account on their end to allow you to accept events with these click IDs.

They may have already done so automatically, but they are rolling this update out slowly to the best of our knowledge. Therefore not all accounts will be allowlisted for “BRAID” parameters, and our events won’t be able to be sent with these click IDs present until your account is allowlisted by Google.

If this is the case, if you have a Google representative please reach out to them to request your account to be allow listed for events with the BRAID parameters, if you don’t, then you can use THIS LINK.

Events not sent because “customer has not accepted the customer data terms”

Read this if you see an event has not been sent and you see the following error in the status column:

To accept the terms and conditions inside Google go to “tools and settings” on the top right and select “measurement” and then “conversions”. You’ll then see a “settings” tab on the left which will allow you to access the customer data terms as shown here:

Please ensure this has been accepted. If it has and you are still seeing this error moving forward, please reach out to support and send a screenshot showing that the terms have been accepted so our team can investigate further.

Events not sent because “Actions which use the one-per-click counting type cannot be used with gbraid or wbraid”

This error message will look something like this:

If you see this, it’s likely because the event “count” setting is set to “one”.

Types of conversion counting options are explained by Google HERE.

To fix this issue, please ensure this setting is set to “every” for the event by following these steps:

1. Sign in to your Google Ads account.
2. In the upper right corner, click the tools icon , and under “Measurement”, click Conversions.
3. Click the name of the conversion action you want to edit.
4. Click Edit settings.
5. Click Count and select One or Every.
6. Click Save, then click Done.

Events not sent because “your account does not have a conversion action with a name that matches the label of this conversion”

The error message should look look something like this:

This error message often occurs because we are only looking for conversions actions with a “conversion source’ that is some form of import source, most commonly this source is “website (import from clicks)”.

If the conversion action does exist but with a conversion source which is not an import source, then unfortunately it is impossible for us to send the event to that specific conversion action because of restrictions set by Google.

You can check this by going to your conversions list and seeing the “Conversions source” column as you can see in the following example:

In this case, the only conversion action that we can send events to is “Purchase Example” because this is an import source. The other 3 conversion actions are just website sources, and therefore do not except any imported events.

If your conversion action is not an import source, then you must send Hyros events to a different conversion action or create a brand new one following the standard setup. Google does not provide a way to change the conversion source of an existing conversion action.

Enhanced conversions for leads not enabled in the Google Ads Conversion settings page

If we get this alert from the Status Column in your Sales Data section it is required to check the right settings are enabled on Google Ads.

From your Google Ads account please go to Tools and settings > Conversions (under Measurement) and then click on Settings on the left side:

From this screen confirm the Enhanced Conversions for Leads setting is enabled and save your settings.

This setup can be completed in 2 steps, with an optional 3rd step should you wish to deduplicate events more accurately.

If you have catalog campaigns and wish to optimize around Hyros events, please also view the drop down labelled “Using Hyros events with Catalog Campaigns” below.

Step 1 – Configure Events to be Sent From Hyros

Please see the video guide:

Step 2 – Check Pixel Settings and Confirm Deduplication

Please note this video refers to server events from Hyros. If you have only just activated this feature, you may need to wait for some more Facebook events to be tracked in Hyros and then sent to Facebook to be able to successfully follow all of the steps.

Hyros sends events hourly so our server events will not be immediately visible.

Please see the Video Guide:

If you notice that deduplication is “not meeting best practices” inside Facebook, then they should be able to provide more information as to the exact issue inside of Facebook.

Also if you have multiple Facebook pixels on your site, this will weaken deduplication.

You can also see the “Facebook Event Troubleshooting” dropdown below this section for more information and other troubleshooting steps.

Step 3 (Optional) – Adding Event ID Deduplication

Please note that by default Hyros will track Facebook’s “FBP” cookie value and send this with events when it is available. This will normally allow Facebook to deduplicate events without any extra edits to code.

However this step should be followed if:

• You do not want to rely on Facebook’s “FBP” cookie for deduplication alone.
  Although this automatic method should be fairly reliable, because it relies on Facebook’s cookies, deduplication may not always be successful.
  Use the event ID if you would like an extra layer of security to ensure deduplication occurs successfully as much as possible.
• You are able to manually add the pixel to your site. This setup requires editing the pixel code used by Facebook to track standard events.
  As each business is different, if you are not sure how to find this, we advise using this documentation from Facebook to understand how this code should look: https://www.facebook.com/business/help/402791146561655?id=1205376682832142
  If you have not added the pixel manually yet to your site, you will need to remove the current pixel implementation and use the Facebook documentation above to install the pixel and track your standard events manually.
  For example, the Purchase event code should look like this on your site, which is the part we will need to edit: fbq('track', 'Purchase', {value: 0.00, currency: 'USD'});

To set this up, please follow these 2 steps:

1. Turn on “Enable Event ID Collection”

2. Add the Event ID Code to the Standard Event you want to Deduplicate

We are going to use the standard Facebook “Purchase” event as an example in this case, because this is the most common event that people will use with Hyros, however please ensure this is done with any other standard event you are sending Hyros events to.

First, copy this code, this is what you will need to add to the standard event code in the Facebook pixel:

{eventID: Math.random().toString(36).substr(2, 15)}

Next, find the standard event code you have manually installed on your site, it should look something like this:

fbq('track', 'Purchase', {value: 0.00, currency: 'USD'});

Paste the event ID code directly before the final curly bracket with a comma and space separating it from any previous text, just like this:

fbq('track', 'Purchase', {value: 0.00, currency: 'USD'}, {eventID: Math.random().toString(36).substr(2, 15)});

Please copy this and add the new standard event code back to your site or add the event ID to your current Purchase code in exactly the same way.

WARNING: IF YOU ARE ADDING THE EVENT ID TO ANY OTHER EVENT

As you can see above, the purchase event code has 4 “arguments” or parameters, all separated by a comma. These are broken down below:

1. ‘track’
2. ‘purchase’
3. {value: 0.00, currency: ‘USD’}
4. {eventID: Math.random().toString(36).substr(2, 15)}

The event ID section MUST always be the 4th argument. When configuring any other event with the event ID, because there is no value or currency for most events, we must add a blank argument in the event code instead to ensure the event ID is always the 4th argument as shown in the example of a lead event code:

fbq('track', 'Lead', {}, {eventID: Math.random().toString(36).substr(2, 15)});

You can see the extra {}, above which needs to be added for other event types. Please note that if this is not done, Facebook will not be able to read the event ID and use this information for deduplication.

That will conclude the setup, please ensure you have done this with all other standard events that you are sending Hyros events to.

Please note that this guide is for the catalog campaign step ONLY, please ensure you have also followed the “Main Setup” steps to allow events to be sent correctly, then you can proceed to the steps outlined below if you have catalog campaigns:

How to Link the Facebook Pixel to Your Catalog

Please follow the steps from Facebook’s documentation HERE to connect your pixel to a catalog.

Please take in mind that Hyros will send the SKU with the sale into Facebook, and use this as the content_ids field. Because Facebook specify that this field for each product should match exactly with the ID of that product inside the catalog, you need to ensure that your ID inside the catalog is the SKU of the product if you want to utilize Hyros events for optimization.

Once you have connected your pixel to a catalog, then you can follow the steps below to set the event to optimize around Hyros events.

Please note this video specifically covers what you need to do if you are sending Hyros events to a seperate pixel, however if you are sending Hyros events to your existing pixel following the main setup guide, you can simply continue to use your existing pixel:

Conversion Rules are a great way to customize where you send events to and what is and is not sent based on pre-set conditions. Although there are plenty of other creative ways you can use this, in this guide we will cover some of the most common ways of using this feature, such as:

• Blocking Recurring Sales.
• Blocking free trial events or sending free trial events to a separate custom event.
• Splitting up sale events depending on which store sales were generated from.
• Splitting up add to cart events depending on which store they came from.
• Optimizing around qualified leads only.
• Blocking unqualified calls.
• Sending a product or group of products to a unique event.

To add any conversion rules, select the “conversion rules” button at the bottom of the “conversions” tab in the Facebook integration settings:

Then you will have a selection of tabs based on what type of conversion rule you would like to create. If you want to adjust how sales are sent to Facebook, you will need to add a “sale rule”, for adjusting call events, you will need to add a “call rule” and so on:

Please find exactly what you are trying to do from the below examples and follow steps:

These are some of the most common ways of using conversion Rules, but please let us know if you would like to do anything else and we would be happy to assist you with your unique situation.