Rate this page
Did you find the information on this page helpful?
1 Star = "not helpful"
5 Stars = "very helpful"
Feedback
Please tell us what you think about this page.
 Your message to us:
|
The URL Pattern Application Programming Interface (API)
The BeeTagg System’s architecture allows an easy integration of already established applications. Though several BeeTaggs can be linked with static URLs, the service thereby is very limited if not even made impossible.
If one wants to link 1’000’000 user profiles or, for example shop articles, the static approach would quickly reach its own limits. With 1’000’000’000’000 BeeTaggs, as it is the case in the BeeTagg for eBay application, it would even be impossible.
This Is How It Works
The BeeTagg URL Pattern API allows the service of dynamic URLs. Thus, every BeeTagg gets linked not anymore with a static URL, but with a so-called URL Pattern.
The URL Pattern consists of any URL that can be amplified with placeholders and attributes.
Here you can see the adaptive attributes:
code
|
The BeeTagg in its hexadecimal design
|
link
|
The URL pattern of the Range (incl. placeholders)
|
codeoffset
|
The BeeTagg’s offset within its Range
|
rb
|
The first BeeTagg within the Range
|
re
|
The last BeeTagg within the Range
|
ulang
|
The users language (if existent)
|
clientid
|
The client-installation’s unique ID
|
agent
|
The user’s useragent (if existent)
|
uid
|
The user’s unique ID
|
title
|
The title of the URL
|
screenwidth
|
The user’s width of the screen in pixels
|
An example for a URL Pattern:
http://mobile.ebay.de/showarticle?id= %(codeoffset)&lang= %(ulang)&sw= %(screenwidth)
The most important attribute is the so-called Code-Offset (codeoffset). The Code-Offset indicates the position (index) of the BeeTagg you clicked on within the Range.
Example: Integration of The BeeTagg System Into An Online Shop
We will now show you on an example how to use the URL Pattern API:
A customer wants to provide all articles (5’000’000 articles) in his online shop with BeeTaggs in order to promote them in the newspapers, for example. If a user clicks on the BeeTagg in the ad, then, he shall be directly connected to the respective mobile shop page to buy the article or to get further information about it (e.g. reviews, etc.).
Assumption: The shop’s data bank has a sequence number (index), starting with 1 and ending with 5’000’000, for every single item.
1. Step:
A new BeeTagg Range with the extent 5'000'000 is being applied. The extent can be arbitrarily adjusted, as well as extended at a later date.
Every BeeTagg within this range has now an offset between 1 and 5’000’000.
2. Step:
A URL pattern is being defined for the applied range:
http://www.meinmobileshop.com/zeigeartikel.aspx?id=%(codeoffset)&lang=%(ulang)&sw=%(screenwidth)
Done!
The Redirect
If now, one clicks on the BeeTagg of the article with the sequence number (index) 210, the dynamic URL gets calculated at the Redirect and will then be send back to the mobile phone (client).
A possible URL which the mobile phone would access could be the following one:
http://www.meinmobileshop.com/zeigeartikel.aspx?id=210&lang=de&sw=176
The shop-application now knows that the article with the sequence number 210 has to be displayed in the mobile phone browser.
Moreover, it contains valuable information on the mobile phone and its user. It detects that the preferred language of the mobile phone is German and that the display has a width of 176 pixels. In this way, the User Interface can be adapted perfectly well to the end device.
|