

Be sure to create your landing page first before setting up a campaign in Google Ads. For this documentation, we will be using SendInBlue for making the landing page. If you want to check out other options to create landing pages, visit this article. It is important to take note that we can use any services to make the landing page. The most important element when creating a landing page is having a form. This form will be used for collecting the lead’s email address. We’re only using SendInBlue since it automatically adds the lead’s email address into a contact list once they’ve used the form on the landing page.
On your landing page editor, make sure you’ve selected what list will be used for adding the lead in once they’ve used your form. Below is a screenshot of SIB Landing Page editor.
Based on the screenshot above, the email address and SMS number of the lead will be added to “TEST CONTACT LIST” in “CRM Folder” after they’ve used the form.
Publish the landing page and copy the URL of the landing page (You can also have it embedded into your website if you don’t want your upcoming leads to see the URL).
Above is the landing page we just published! From here your leads will enter their email address and SMS number (You can also have that change in SIB’s landing page editor). Once the lead pressed on “Start Today!”, they’ll be redirected to this page.
After that, the lead’s contact details will be automatically added to the contact list we created in SendInBlue.
Once you have published your landing page and have made sure that it’s working correctly, it’s time to connect it to your Google Ads Campaign.
One way to reach customer engagement is by sending them emails welcoming them to your site. Your email could be a discount code once they used the landing page form or it could be a well-informed description of your site. Now, we do not want that to send manually since it takes a lot of resources. With SendInBlue, we can automate the sending of these emails with the use of their email automation workflow, and implementing them only takes a few minutes.
Now, all it is left is connect the landing page to your Google Ad Campaign. Our objective for this chapter is to have the user redirected to the landing page once they have clicked the ad we’ll be making.
Note: For this documentation, we will be solely focusing on implementing the landing page into a Google Ads campaign. We recommend to embed this landing page into your website and/or host it directly to your server since SendInBlue’s Landing page generates the domain, randomly.
7. Paste the tracking code into your landing page. This needs to be pasted in the <head> tag on your page. SendInBlue’s landing page editor makes the implementation easier by just opening the settings window. (Some parts were blocked for security reasons).
8. Be
sure to publish the landing page again so that Google Ads can detect the tracking code.
9. Press Save and Continue to go to the
next step
10. Name your campaign and make sure the two networks are checked. This will expand the availability of your ads.
13. On Budget and Bidding, you’re required to enter how much you’re willing to spend for your ad on Budget. For Bidding, you’ll be asked if where do you want to focus on the campaign (eg: Conversions, Clicks, etc). For this documentation, we will be using the following options:
Since Google recommends to stick to Conversion as the bidding, we’ll use it.
14. Below are the other available options for Budget and Bidding. However, we’ll be using the default settings for this documentation
Some ads are also complex that can display more links and descriptions. Below is a sample of that ad about an online shopping site popular in South East Asia
Based on the screenshot above, ads can have multiple links as well as headlines and descriptions. This is possible by adding multiple headlines and descriptions, as well as ad extensions.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |