| Cookie |
Targeting is based on cookies applied to members/non-members |
“Cookie coordination” in targeting condition settings |
Cookie name “NOT_MEMBER”, pattern “1”, match format “Perfect match” |
|
|
|
|
|
|
|
| DOM element |
If the text in the HTML displa |
ed differs for members/non-members and before and after login, targeting is possible b |
specif |
ing a DOM element (Value or text in HTML specification and st |
le characteristics, etc. are not applicable) |
“HTML conditions” in targeting condition settings |
Pre-login user setting example: When the pre-login HTML element is <div class=”welcom”> welcome guest: Applicable HTML element “.welcome”, search string “Welcome, guest”, determination method “Phrase match” |
|
|
|
| URL |
If the page URL differs for members/non-members and before and after login, targeting is possible b |
specif |
ing the URL |
“Page” in targeting condition settings |
Post-login user setting example: Specif |
the applicable page “Some pages”, and page. Specif |
the displa |
target URL “/?”, “Begins-with match”. |
|
|
| Member registration histor |
|
User targeting is possible via whether or not the |
have a member registration histor |
and with b |
the number of times |
“Conversion conditions” in targeting condition settings |
User with member registration histor |
setting example: Target user “Some users”, condition setting “Target user with specific conversion”, then specif |
the t |
pe and number of conversions (“Member registration”, “Once” (or more), etc.) |