Part TWO: PLATFORM MIGRATION SCENARIO: GOOGLE EXPANDED TEXT ADS AND LANDING PAGESJuly 29, 2016
Post originally appeared on Medium here on 7/28/2016
Part TWO: PLATFORM MIGRATION SCENARIO: GOOGLE EXPANDED TEXT ADS AND LANDING PAGES
Jumping right in…this week we have had 6 discovery calls leading to 6 immediate demos around Google’s Expanded Text Ad requirements.
DevHub solves for the “proxy URL deprecation,” or “deprecation of Whitelisted Proxies.”
Here are some of the ways we handle proxies within DevHub:
1) Domains You Register or Control (no customer involvement needed)
a) Group sites underneath a common domain (most proxy tech supports this)
b) Register a domain for the customer, dedicated to the proxy
c) Register a domain for the customer and use subdomains for each campaign
2) Domains Owned by Customers
a) Proxy lives as a subdomain of the customer’s primary domain
Customer Involvement: Customer must set a DNS record to point to our servers
b) Proxy lives under a subdirectory within their primary domain
Customer Involvement: Customer must give access to their server configuration or have a tech contact on their side that can do this for them. Not all hosting providers will support this option.
With our proprietary migration tech, we are able to match sites/ landing pages 100% so our customers and their end customers do not know the difference. Unifying all disparate landing page campaigns, websites, vertical specific solutions on DevHub is easy and safe; which is quite the opposite of how companies use their CMS today.
Every company needs DevHub to build a scalable future…it’s a mindset.