Wildcarding URLs

Ensure engagements display properly

Guided tours, tooltips and named features are specific to URLs. However, some URLs contain dynamic content and change based on the user, account, session, or numerous variables. 

If a page of your web app contains information specific to the user, account, or other dynamic data in the URL, this information can be replaced with a wildcard (an asterisk *).

How to wildcard a URL

To wildcard a URL, replace a certain portion of the URL with an asterisk. 

Example:

testpage.com/home/johndoe26 -becomes- testpage.com/home/* (by replacing johndoe26 with an *)

johndoe26.testpage.com/payment/ -becomes- *.testpage.com/payment/

Wildcarding can also replace the remainder of a URL, see below:

testpage.com/home/example* (would include anything after example) 

testpage.com/home/example_test

testpage.com/home/example_experiment

testpage.com/home/example1

Replace the subdomain and additional items in a URL

*.testpage.com/home/*/homepage includes:

test1.testpage.com/home/user1/homepage

example2.testpage.com/home/account2/homepage

sample3.testpage.com/home/role3/homepage

Ensure page names represent the same web page

When a page is referred to by name, wildcarding the corresponding URL ensures that the correct web page is referred to, regardless of the page URL. This is especially relevant for dynamic URLs that are based on user attributes. If a payment page URL is dynamic, but the page itself is wildcarded as Payment Page, all references and engagements on the payment page will still function properly.

LookupValues

Naming the correct URL dynamically

Similar to wildcarded URLs, URLs with lookup values are designed for dynamic URLs, however, they are modified strictly based on the user attributes of custom variables that are passed to UserIQ.

How to use a lookup value

To use a lookup value, replace a certain portion of the URL with %%, the custom variable name, and %%.

Custom Variable names are shortened names of user attributes. They normally have underscores to separate words. They can be found in the user attributes of any user.  

Example:

testpage.com/home/johndoe26 vs testpage.com/home/%%user_id%%

johndoe26.testpage.com/payment/ vs %%user_id%%.testpage.com/payment/

Lookup values will only use the custom variables that are being sent by the user.

So, if John Doe, user id johndoe26, of Acme Corp was your user, his pages will be:

testpage.com/home/%%account_id%% == testpage.com/home/acmecorp

testpage.com/profile/%%user_id%% ==  testpage.com/profile/johndoe26

or

%%account_id%%.testpage.com/home/%%user_id%% == acmecorp.testpage.com/home/johndoe26