Retainer Client Onboarding Steps for AMs

These are the steps AMs should take to delegate work to internal team members and to request information from clients

• Have the client add marketing@gk3capital.com as an admin to the client's CMS (website backend)

• Assuming the client is on the small side and doesn’t have an IT team, request the login information for their DNS provider (typically GoDaddy)
  • If the client does have an IT team, we don’t need login information. We will send instructions to the IT team instead of implementing changes ourselves

• Assuming client does have their own Google Ads account, ask the client to add marketing@gk3capital.com as an admin in their Google Ads account. 
  • If the client doesn’t have a Google Ads account, reach out to Brett to create a Google Ads account for these guys and let me know once finished so I can connect to HS

• Assuming client does have their own Google Analytics account and Google Search Console account, ask the client to add marketing@gk3capital.com as an admin in their in these accounts
  • If the client doesn’t have a Google Analytics and Google Search Console account, reach out Ethan to create these accounts for them under GK3s parent account and provide the client emails to add to these accounts 
• Assuming the client does has a dev team, have the client add the following tracking code to the global header tag:

<!-- Start of HubSpot Embed Code -->

<script type="text/javascript" id="hs-script-loader" async defer src="//js.hs-scripts.com/46162885.js"></script>

<!-- End of HubSpot Embed Code →

Your instructions to the client can say something to the effect of “Please place this code in the global header of the website so that it tracks every page on the website”

• • If the client doesn’t have web developer, please give these same instructions to Rocky once he has access to the website backend. 
• If the client has an IT team, send them the following instructions to set up subdomains for the blog, landing pages, web view email, and sending domain:

Create the following 3 DNS records with the following information to create subdomains:

1.)

Record type: CNAME

Host: pages

Required data: 46162885.group35.sites.hubspot.net

TTL: 1 hour

2.)

Record type: CNAME

Host: blog

Required data: 46162885.group35.sites.hubspot.net

TTL: 1 hour

3.)

Record type: CNAME

Host: email

Required data: 46162885.group35.sites.hubspot.net

TTL: 1 hour

Create the following 3 DNS records to establish the email sending domain:

1.)

Record type: CNAME

Host: hs1-46162885._domainkey

Required data: nepsisinc-com.hs12a.dkim.hubspotemail.net.

TTL: 1 hour

2.)

Record type: CNAME

Host: hs2-46162885._domainkey

Required data: nepsisinc-com.hs12b.dkim.hubspotemail.net.

TTL: 1 hour

3.)

Record type: TXT

Host: _dmarc

Required data: v=DMARC1; p=none;

TTL: 1 hour

Update the following record for the email sending domain:

Record type: TXT

Host: @

Required data to be included with current data: include:46162885.spf07.hubspotemail.net

• • If the client doesn’t have a IT team, ask Ethan to retrieve this information and add it to the client’s DNS. 

• Link the style guide on the onboarding card 
• Work with Tanner or Tom to create three generic email headers based on the accounts style guide
  • Let Ethan know once these have been created so Ethan can add them to the HubSpot account
• Ask for the clients IP addresses for any team members who go to the website so that we can filter out that traffic data
• Ask the client the following (this isn’t necessarily needed right away to complete onboarding but at the very least, this information will be needed early on in the GK3/client relationship): 
  • What users should be on form notifications?
  • How should users be assigned contacts from here on out/who should be assigned contacts?

• • Do they have contacts that need to be imported into HubSpot? If so, give those lists to Ethan