When you click on “Create button” either on the Piggy Bank or on a website you defined, you’ll get to the input form.
First of all, you will need to name the button, so name it well so you don’t get lost when you have dozens of them.
All selectors on this section are dynamic, and the sample button is updated when you change your selections from the controls.
The most important part here is the button caption. You must type in here a straight message to anchor potential tippers or customers.
And there it is the Default coin. If you select a coin from here, then you will be limiting your button to that coin only. If you choose “None”, then you will be able to select which of all supported coins you want to request for.
When you set a default coin, you will only be able to get amounts of that coin, specifically.
When you don’t set a default coin, you will be able to get either an exact amount or a minimum amount of any coins you want, or even specify an amount in USD and let the potential senders select the coins they’ll send in the amounts they want to fulfill your request.
And then you have the Button logo. It is up to you if you want to show the white puma (the default logo) or any coin logo. If you are a Premium User, you may also put your website logo (as defined in the website settings) or a custom one you can upload.
All of the buttons can include a counter of the coins you’ve received (unless you decide to hide it by checking the “Hide counters” checkbox).
For instance, this button shows the counters:
And by changing the type from button to table, it shows the breakdown of who sent the coins and when:
You may decide to show who sent you coins but not the counters by checking the “Hide counters” checkbox:
As you may notice, the counters below the caption aren’t shown here. It is up to you to decide.
There are two request types:
Suggestion:select this type when you want to suggest an amount for
every coin you want to support in your request. When the widget is
invoked after clicking your button, the minimums will be preset and
the users will be allowed to specify any amount above that.
This type is the recommended one if you want to ask for coins converted from any fiat currency.
this type if you want to get a specific amount of any coins.
This type is not recommended for fiat to crypto conversions.
If you defined a default coin for your request, you will only be able to specify either a fixed or a suggested amount of that specific coin. You can’t access the fiat conversion capability of the widget.
But if you didn’t set a default coin, you will be able to select from the other dynamic schemes:
· Per-coin direct values: either on a fixed or a suggested type, you specify here the amount of coins you want to get. Just check the boxes of all the coins you want to include (all of them if you want) so the potential sender decides.
· Converted from fiat value: either on a fixed or a suggested type, you define how many coins in a fiat currency you want to get, and check the boxes of all the coins you want to accept. There are minimums, so you must specify a value that goes above the minimums. You should try to specify an amount some cents above the minimum to avoid a loss in a price drop.
If you’re completely lost with it, you can check the next samples:
The user will not be able to specify any amount and only the default coin will be shown:
The user will be allowed to select only one from the coins you requested:
This case is similar to the “Fixed amount, single coin” example. The difference here lies on the ability to specify the amount to send (the coin amount input box is unlocked):
This one is similar to the previous, but the user can select more than one coin to and also specify the amount to send:
Finally, when suggested from USD is selected, the widget behaves just like the fixed from USD mode, allowing the user to select more than one coin and specify the amount to match the requested minimum:
The next options are available on buttons that aren’t part of the Piggy Bank, but from a website container.
By default, the <title> and <meta “content”> tags from the page where the buttons are embedded are used to identify where the coins are being categorized into, so you will have different counters for coins on the same button across all your page.
Let’s say you put a button on your website to gather donations to keep it running. From page to page, the button will show different counters and record data, because the widget is detecting it is being invoked from different pages on your website:
As you may notice on this screen shot, this button is showing the URL of the post on our forum shoutbox as entry id because the widget was invoked from there.
Here you can see that the same button is showing the URL of another post on the shoutbox as the entry id. This will mean that tips sent through this page will not be counted at the other page and vice versa.
To avoid that behavior, setting entry data will group together the counters no matter where are they placed:
Then, no matter where the button is embedded, the entry identifier and title will remain unchanged:
As you should have noticed, by setting an entry id (also an entry title to favor consistency) allows you to define site wide buttons, so you can have your site wide ones apart from the specific usage ones.
Let’s say you have an army of fans and they want to start a campaign for you on other websites, but you want to keep track of who has turned more people in. Here is where you can set a comma separated list of keywords and give your fans their own unique keyword to do the job.
Referral codes are not mandatory for the widget to maintain. On the invocation code, you can set whatever you want as referral code, but we give you this field to help you remembering those you created.
Anything you specify here is actually used by the code generator to build up the links you want to give to every one of your fans:
They do not affect the button counters themselves, but when a conversion takes place, you will be able to see the breakdown on your analytics page.
Let’s say you have a multi-author blog and you want your engine to automatically put a “Tip the author” button below the post’s content. Under normal circumstances, you may think on creating a button for each author and give them the invocation code for their respecting buttons or maybe creating a button and giving them referral codes. But in either case, all the coins gathered are going to your account and not theirs.
Here is when the target overriding comes in place: you can set into the invocation code the email of the author as target, so when someone wants to send some coins, they go to the right person.
When you specify a target, the email you provide is searched in our accounts database. If it is found, the order goes straightforward and notifications are delivered to both the sender and the target. If the email is not found, a new account is setup using that email as a reference and an invitation is sent.
This is one of the advanced topics discussed on the Parameters reference section. You could safely ignore it if you are not going to use the button’s advanced topics like this one. But if you can programmatically set this or other information, or you want to know the engine’s internals, then take a deep look at the Technical specifications section.
You will be able to specify information here only if you have upgraded your account to Premium.
Normally, the widget shows a prebuilt description for the operations that it would perform if an order is submitted:
But when you specify a description, it is prepended:
The sole purpose of this feature is to let you inform your potential senders what are you willing to do with the coins, what are you going to give in return or other info related to the order you want them to submit. This is most helpful for selling goods or services through the platform.
As mentioned on the logo settings, you can set a custom logo to your button. You need to build a 256x256 pixels 24-bit PNG file (preferably with transparent background) and set it to your button, so when it is rendered, the logo is placed on the button:
This is another topic suitable for automated tasks.
If you plan to deploy the button on a storefront, you may need to create a script on your website to receive transaction info when an order is placed so you can internally trigger anything you need to deliver whatever the user acquired with their coins.
So, at the moment an order is confirmed, the script posts all the information to the URL you provide, giving you all the details we can provide.
Please take a look at “The callback functionality” section on the Technical specifications to learn how to use it.
As you may encounter a “The Analytics” section, there are two types of them:
· Public analytics show the same information that can be seen on the buttons: the counters and the details table, but nothing more. This is the default mode for all buttons and it may be perfect for transparency in front of the potential senders. A link to them is provided within the widget so everyone can take a look at them.
· Private analytics are rich in detail, and they can only be accessed by registered users. Here you can see a full breakdown of who, how, when and why.
So, since Premium users may have commercial affairs with our platform, they would like to keep all their transactional records private. That’s why this option was added.
|© 2018 Blockchain Financial|