I am completely new to branch.io. And I am trying to incorporate this into my project. I have a use case where a person will send an invite link using branch to attend a meeting. Also this link should be unique to the invitee. Once user receives a message with link he will click on the link and it should take him to a webpage(my own)/Deepview(branch.io), where he should be able to submit the form which will register him for the event. Once he finishes the registration, show him the page where there is a download app link.
So far I looked into branch.io documentation but i am confused what all features i should use. This is what i found so far. let me know if this is suitable for my use case or not.
For the first scenario of sending unique links i was thinking of using branch.io API as this is what their website suggests
Secondly on click of link taking user to some landing page. this is the part where i am very confused. I didn't find any article which says i can submit a form in Deepview. Or do i have to use my own webpage where user will submit the form and then get that information and send it to braze to create another Deeplink which will take user to app download page.
Please suggest me the features of branch.io, that I should use for my use-case
thank you for contacting Branch. You can create a unique Branch Link with the following ways based on your situation.
Use Quick Links or Ad Links from Branch Dashboard for fast link creation and easy tracking.
Use our App SDK to create and share links within your app.
Use our Web SDK to create links which help convert your web users to app users.
Use our HTTP API to programmatically create links from your server.
Use our Chrome Extension to generate links from your browser.
Also, you can set a different final destination (User landing page) in your Branch Link for your app based on your purpose. For example, you can make users who do not have your app in their device can land on either the App Store, Deepview (is a mobile web splash page, hosted by Branch), or specific webpage via your Branch Link according to your needs.
Please feel free to contact support#branch.io if you have any further questions. We are happy to help you.
Related
The long version of a Firebase Dynamic Link is not firing the events First-opens, clicks, re-opens...
Is that a bug or is it on purpose, and in that case why?
Background:
I cannot use the short version because I am adding programmatically a parameter in the deep link associated, hence I need the long version to accomplish it.
As a work around: how can I add programmatically a url parameter in a short Firebase dynamic link? I don't want to generate programmatically a link, I want to have only one link which has dynamic value on it (e.g. productID for a link in my product detail page)
Thanks for your help!
Need your actual dynamic link to investigate this.
At the same time I can suggest that you can create short link programmatically. See iOS docs, Android docs and overview.
EDIT:
When you say analytics what of the following you are referring to:
Data shown in Firebase Analytics (accessible from Firebase Console
in Analytics section);
Data shown in Dynamic Links Analytics (accessible from Firebase Console in Dynamic Links section);
Data shown when in list of created dynamic links you clicking on specific link;
Data retrieved using Firebase Dynamic Links Analytics API;
I feel that we should account long links clicks in 1 and 2. I did not get yet confirmation from server side folks to be sure about this. I would trust Ian's comment for now.
In 3 will be shown only short links created in Firebase console. Short links created using API will not show up in 3.
In 4 you can access data related to short links.
I today get Instagram api and add my website live,
I see write:
Client Status: Sandbox Mode GO LIVE
I can't click on ''GO LIVE'' button why ?
You would need to start a submission for approval to go live, though:
Feeds for websites won't be approved; these will remain in sandbox mode and be limited to 500 requests per hour and 20 images. This doesn't sound like much especially for large clients, but if you cache your responses, it's not a problem.
The main confusion is because they have made it sound like every app/feed has to be approved and out of sandbox mode to work, where as the reality is that only fully functioning apps for phones, or a widget plugin really ever need to be.
You will no longer be able to display feeds based on hashtags, only a users own photo's. By getting a client to be a sandbox user, is how you can access their feed without their login information.
Older apps/feeds will need to be updated to use the new code before June or they may stop working.
It's mainly to stop apps hammering instagram's servers for unlimited requests on any hashtag/users they like.
Here is an example of how to fetch and cache images using WordPress's 'set_transient' - you will need to use a loop to output the data.
WordPress Instagram Gist
Here is the relevant piece of information in the dev docs:
Here are some examples of scenarios that will not be approved:
To display content for a personal website. If you are a developer and you want to showcase Instagram content on a website, then you do not need to submit your app for review. By using a client in sandbox mode, you will still be able to access the last 20 media of any sandbox user that grants you permission.
One-off projects. If you are an agency building websites or other integrations, note that we don't grant permissions to clients created for one-off projects. If you are interested in building a product, platform, or widget that will be used as a service across multiple projects, then you may submit a single client_id that you can use across multiple projects.
To use a widget. If you are installing a widget for your website, then you do not need to submit for review. Some widgets may ask you to create a new client id, but you do not need to submit it for review for the widget to work. Your client can remain in sandbox mode and the widget will have access to your last 20 media.
Hope that helps clear some confusion.
I have a number of APIs both authenticated and not authenticated, created in earlier versions of import.io.
With the new Windows app I can't create an API, or at least pick one up. The tutorial shows a whole bunch of options, but I only get "CONFIGURE" and "EXPORT". "Configure" only gives me the option of single URL, bulk extract and URLs from another API. But there is no link to give me the API address.
Similarly, EXPORT only provides "USE IN DATA SET".
I asked their support but got this:
Hi Glenn,
Thank you for reaching out.
As you may noticed, we made some changes to our interface.
We moved the into the Export tab (next to configure) and named it
simple API integration.
Let me know if you have any questions.
Thank you,
But when I replied that I don't have that option, I got no reply.
What am I doing wrong?
Glenn.
Import.io support got back t me after I sent a screen video (http://www.evernote.com/l/AAhMJsy7INVHFauEOGFQBgEgJq2IPRSA6AU/). There's a bug in the new Windows desktop app that prevents authenticated APIs from showing.
I want to post a message on google plus business page. Is there any way to do this.
I am confused between interactive post, app activities and moment.
Should I use Moment to post on business page?
I go through google api site documents, but not getting any solutions.
Please let me know if there is any other way to post in google plus page.
It depends on exactly what you mean by "post" and by a "business page".
I'm assuming that the "business page" is one that is not associated with a Google App account. If you're meaning something that will show up on your stream, and that people who have you in a circle will see your post - there is no public API from Google that will do what you want. You need to work with one of their partners, such as HootSuite, to automatically share messages to your stream.
Interactive posts are ways that a visitor to your website can be prompted to share something from your site to their stream on Google+. These interactive posts include both a link to your site as well as an additional "call to action" button to an individual item from your site. It does not automate posts, although it can make some parts of it easier.
App activities and moments are the same thing. They are meant to record actions that take place on your website on Google+, but they do not directly share anything into your stream. Instead, they create an event in your Google+ profile that can be seen only by those you permit it to - you can then, if you wish, share that event to your stream. So while the moment can be generated automatically, it still requires manual action to share it.
Finally, if you have a page that is associated with a Google App account, you can create posts automatically, but those posts are limited in scope. They are only visible to, at most, other people in the same App Domain as the account. This is useful for using Google+ as a communication tool inside an organization, but not useful for communicating with customers, for example.
I am thinking about app that will use google form and I need to create forms from that app. Is there a way how can I create form in google docs without using website but through some api or some other way?
I can offer an idea for a solution using Google App Script.
Since the beginning of 2013 you can create new forms using the App Script Forms Service API quite easily.
var form = FormApp.create(title)
.setDescription(description)
.setConfirmationMessage('Thanks for responding!')
;
The problem now is how to get that App Script running from your non App Script code.
You can use App Script to create a Web App that reacts to HTTP GET requests.
So putting it together, you may be able to create an App Script Web App that reacts to a GET request and when it gets the right URL parameters, it creates the form.
(Nov 2020) Yes, it is possible to programmatically create Google Forms. You can do it with Google Apps Script using its Forms service. You can also extend the code to read in the contents from Google Docs (with Apps Script's Document service) and use it for the creation of Google Forms.
I created a Google Workspace (formerly G Suite) Add-on, which you can think of as a Google Docs extension, called GFormIt. Its original purpose was intended for teachers to write exams/quizzes, possibly with answers, in Google Docs, then automatically convert them to Google Forms to distribute to students who submit their answers into Google Sheets (the destination for Google Forms submissions).
Furthermore, if you (the teacher) provided answers to your test questions, GFormIt would also auto-submit your answers to the Sheet as if you were a student. If you do that, and use a tool like Flubaroo to grade the exam, you could designate your row in the Sheet as “the answer key.” You can learn more about how it works, including viewing a short video, at the GFormIt page linked above.
This Google Docs add-on, along with others for Google Docs, Sheets, Slides, Forms, etc., are all certified/validated by Google and available for free to anyone from the Google Workspace Marketplace. (However, your admins may have to grant permissions for you to try to install them to your corporate Workspace account.) If interested in building your own add-on, please see the developer documentation and perhaps some of my introductory videos to get started, the most relevant being the one linked to at the top of this answer.
Apps Script is a serverless Google technology, meaning you write your code (using JavaScript) in the browser, and it is hosted by & executed on Google servers. If you wanted to create your own web app (and hosted anywhere), you would have to wait for a Google Forms REST API which does not exist at the time of this writing. (If we ever launch one, you'll find its documentation at https://developers.google.com/forms along with the others like Sheets https://developers.google.com/sheets, Gmail https://developers.google.com/gmail, Drive https://developers.google.com/drive, etc.)
Earlier this year (Mar 2022) the new Google Forms Api graduated from Beta. It is more powerful that the previous versions and caters for two main use cases:
Automated form creation and editing: Enables automated form creation
and editing. Enables rapid form generation from large volume question
banks or other data backends.
Reaction to Form responses: The API also enables developers to build
automations for acting on incoming responses. Examples include
developing real-time dashboards or visualizations and triggering
business workflows based on response data.
We have used it to build an integration that Creates documents and slides each time a form is completed: www.portant.co/google-forms-to-docs and it works really well.
I think the other key use case looks like it would be a good fit for you and others looking for a solution like this.
Cheers, James
Sorry, the API doesn't support programmatically creating forms.