Target not working in a lower environment, authorized host not recognized

[benarson]

Good day all!

I'm having difficulty adding a site's lower environments to the list of hosts. I'm following the instructions found at:

What are Hosts and How Do I Use Them? | Adobe Target

This instance of Target is implemented via the web SDK and the lower environments have a different call out to adobedtm.com. Does this affect their ability to be authorized as a host? I'm reading hosts are authorized as Production by default. Does this mean I need to install and implement a lower environment as a production environment first to achieve adding them as a host? Then adjust the implementation on the lower environment to its proper level, then adjust the host in Target for development / staging? 

Am I blocked by the implementation method? Something else? 

Thank you,

-Brent

[VikasOhlan]

Hello @benarson,

Hope you're having a good day! Below are the most common issues for not getting a host registered in Target:

Problem	Explanation
Not yet visited by Target	Adobe Target only auto-registers a domain after it receives a request from that domain with a valid Target client code.
No Target request made	If the lower environment isn’t fully loading the Target script (Alloy or at.js), Target doesn’t know to register it.
Target call is hitting adobedtm.com instead of Adobe Edge	You may have only loaded the Launch script, but not the actual Target payload via Web SDK. Check is there are any interact calls firing on page.
Improper client code	Lower environments must use the same Target client code (from the same Target account).

I suspect that no call has been made to Adobe Target yet from the lower environment, which is likely why it hasn’t appeared under the Hosts section in the Target Admin. Also, it's true that by default, when a new host makes a call, it gets added to the Production environment. But once it appears under Administration > Hosts, you can assign the host and update its classification to Development or Staging, depending on your setup.

Please let me know if this solves your issue!

Regards,
Vikas Ohlan
LinkedIn Profile 

[GigiCotruta · Accepted solution]

Hi, @benarson,

When connecting AEP and Target, I understand that you did it via datastreams.

Check for the configuration of Adobe Target Service inside the Datastream connection. 

Make sure to set it up in your development Sandbox, with target's development configuration. 

It should look like this.

Then, make sure to have the alloy script in your dev page. 

[benarson]

Thank you very much, this solved it for me.

I had the environment set up in Target, but I did not have the property set up to produce the property token. And, as you pointed out, I didn't have the Adobe Target service set up in the Dev instance of datastreams. Thanks!