A client is getting an error message in the Visual Experience Composer (VEC). The message indicates that no property is associated with a particular activity, even though there is a property…

Question

Options

• AThe activity is in the incorrect Workspace.
• BThe wrong entity.id is set for the activity.
• CThe client is assigned to the wrong User Group.
• Dat_property is missing in the Adobe Target request (mbox).

• A
  6% (2)
• B
  9% (3)
• C
  3% (1)
• D
  81% (26)

Explanation

Option D is correct because Adobe Target's enterprise permissions model requires the at_property token to be present in every mbox/Target request so the system can match the request to the correct property - without it, Target cannot identify which property the activity belongs to, producing exactly this error even if the property is correctly assigned in the UI.

Why the distractors are wrong:

• A - A workspace mismatch would cause the activity to be invisible or inaccessible, not trigger a "no property associated" error in the VEC.
• B - entity.id is a Recommendations-specific parameter for catalog items; it has no bearing on property association errors.
• C - User Group assignment controls who can edit activities, not whether a property token is present in the delivery request.

Memory tip: Think of at_property as an ID badge the mbox must wear on every request - if the badge is missing from the request, Target's security bouncer (enterprise permissions) refuses to recognize the property, no matter how correctly it's configured on the server side.

No community discussion yet for this question.