An Adobe Target Architect sends product information via a Target request (mbox) in order to update the product data inside the product catalog for a specific geographic market of a client's website…

Question

Options

• AFully qualified domain name (including sub domain)
• BA custom Target request (mbox) parameter
• CFully qualified top level domain (excluding sub domain)
• DThe at_property Target request (mbox) parameter

• A
  79% (30)
• B
  5% (2)
• C
  13% (5)
• D
  3% (1)

Explanation

In Adobe Target Recommendations, product catalogs are segmented using host groups, and host groups are mapped to specific fully qualified domain names (FQDNs), including the subdomain. When a Target mbox request fires, Target reads the complete hostname of the requesting page and routes entity/catalog updates to the matching host group - making the FQDN the natural, automatic link between a request and its geographic catalog.

Why the distractors fail:

• B (custom mbox parameter): Custom parameters can pass product attributes (e.g., entity.id), but they don't control which catalog receives the data - that's a host-group concern, not a parameter concern.
• C (TLD excluding subdomain): Target's host group matching uses the full hostname; stripping the subdomain would cause ambiguity when multiple markets share the same root domain (e.g., us.example.com vs. uk.example.com).
• D (at_property): The at_property token governs workspace/property permissions under Enterprise User Permissions - it scopes activities and audiences, not Recommendations product catalogs.

Memory tip: Think of the FQDN as a mailing address - you need the full address (house number + street + city) to deliver catalog updates to the right location. A TLD alone is like sending mail with only the city name: too vague to reach the right destination.

No community discussion yet for this question.