Budget: 8000 UAH Deadline: 2 days
Good day, ready to fulfill your order in the shortest time.
Budget: 7900 UAH Deadline: 4 days
Good day ,
The task is clear, such tasks have been performed, the donor has been acquainted.
It will take up to 4 days.
I will be pleased to cooperate
Budget: 8000 UAH Deadline: 5 days
Hello to
I'm ready to start tomorrow, I can start tomorrow.
Budget: 7900 UAH Deadline: 5 days
Good day !
I have a lot of experience in data parsing.
They have done similar projects. Name of Parser AliExpress.
To begin the work, you will need to clarify the details and work out the final table of Excel. Before I start my work, I will send you a check-in.
The technical part is on me.
I will be happy to cooperate.
Budget: 8000 UAH Deadline: 2 days
Good day Ruslan! You described the task well enough, so I have no questions. I’m going to parse with the help of the parser so you can be sure of the quick result, I can also transfer this parser to you after the deal is completed. So you will be able to put the task of parsing the store on a computer. I will be happy to help!
Budget: 8000 UAH Deadline: 5 days
Good day . an interesting task. Write, I will be happy to work with you!
Budget: 8000 UAH Deadline: 12 days
=========================================
Good day Ruslan
=========================================
Ready to fulfill your task. TZ has studied. I can remove content from this site.
Ready to start work. There is experience of parsing the underlying site. Read my reviews.
Budget: 8000 UAH Deadline: 5 days
Good day . The task is clear, ready to spart, but there are a number of questions about the data format on the output (how to display different languages, names of har-k groups, links to the documentation, etc.).
Please note that all the photos are on the site with the watermark of the store. Some of the photographs can be scattered without a watermark, but if the watermark of this type - https://vencon.ua/uploads/goods/154129/additional/thumbs/sauto_1000__wm/magnitnyy-filtr-atlas-mag-1-mf-12-1.jpg - then it will remain.
Budget: 8000 UAH Deadline: 3 days
Ready to perform. I had to do with this site.
The experience of parsing different sites is sufficient.
Examples of portfolio.
Budget: 7800 UAH Deadline: 2 days
and heal. I have been working in parsing for more than 5 years, and I have collected everything in good quality. on the columns. I understood the struggle
Budget: 7800 UAH Deadline: 2 days
Ruslan, good evening.
We have a great experience in data parsing.
I will be happy to cooperate.
A good evening.
Budget: 8000 UAH Deadline: 4 days
Good night ! I was new here, but I had a deal with Parsong. It’s hard to compete with those who have been here for a long time.
Ready to perform the task, in principle, everything is clear. Work is sufficient.
by P.S. On the account of water signs, I can spars without them.
Budget: 8000 UAH Deadline: 2 days
Good day . I'll make the parsing you are interested in. I have been constantly working on automation of action on the internet and parsing for more than six years.
Budget: 7999 UAH Deadline: 2 days
Good night Ruslan! The task is understandable. I am happy to do this work for you. Go to turn!
Budget: 8000 UAH Deadline: 7 days
Hello to you.
I’m developing bots for telegram on NodeJS. Ready to take. Let’s write, we will discuss.
Budget: 8000 UAH Deadline: 2 days
Good evening . Great experience in parsing any level of complexity. It will be ready in 1-2 days. turn to
Proposals concealed
Proposals are currently absent
-
V V 23 October 2022Иногда проще написать на чем Ваш сайт, и приложить пример xlsx. Но зачем искать простые решения?
Current freelance projects in the category Data Parsing
Channel requirements: 1. Content language: Russian or Ukrainian (mixed RU/UA content is allowed) 2. Number of subscribers: At least 500 subscribers 3. Activity: The last post published no later than 32 hours ago 4. Comments: Comments must be open under the posts (through a group or embedded) 5. Quantity: Minimum 15,000 lines 6. Theme: War, news, politics, fights, trash/gore, sports, cars, crypto, fishing, and others Data to be collected for each channel Mandatory fields: Channel name username (link) Number of subscribers Theme (news, crypto, humor, business, etc.) Language (RU / UA / MIX) Date and time of the last post Presence of comments (yes) File format: Google Sheets / Excel (.xlsx)
Good day! Two tasks need to be completed: 1. Develop a product parser from an external website (10–40 thousand items, marketplace) with structured data saved in MySQL for subsequent output in WordPress. 2. Install and configure n8n on VPS, as well as organize AI content processing: prompt setup, text rewriting, image processing, SEO optimization, and text checking for AI detection. You can estimate the cost of completing both the entire project and each task separately. .
It is necessary to perform parsing from Viber channels (Total number - 49 channels, about 80 thousand subscribers).
Good afternoon. I need a keyword parser that outputs results through a Telegram bot. How it should work: Automatic search on 4 websites for keywords that change from time to time. Search queries are sent every few minutes. The words are uploaded in the form of a .txt file. The Telegram bot should have buttons: start bot, stop bot, download file (downloads a file with active keywords), upload file (uploads an edited file with new words). The bot should ignore previously found results, i.e., it should not indicate the same ad twice. The result comes to the bot in the form of a link with a photo, but just a link is sufficient. P.S. searching websites without API, VPS with 6TB and 50 IPs are already available. For detailed information, please contact me via private message.
Task: one dashboard with all business metrics — advertising, funnel, payments, manager performance, revenue planning. Data is pulled automatically via API. Scope: only the YCL direction (employment in Europe). Kommo has other directions — only YCL funnel deals will be included in the repository (filter by funnel/tag to be agreed upon).1. Data Sources (Integrations) Kommo CRM — leads, deals, funnel stages, responsible persons, sources, dates of transitions between stages (must keep history), reasons for refusals, custom deal fields (see point 2). Stripe — payments, amounts, statuses (success/failure/refund), linked to deals. Meta Ads — expenses, impressions, clicks, CPL, leads by campaigns (currently operational). Google Ads, Reddit Ads, LinkedIn Ads — planned; architecture — extensible connectors without core rework. SEO/organic— Google Search Console + GA4. Cross-link: traffic source → lead in Kommo → payment in Stripe (UTM, deal ID in Stripe metadata — propose the mechanism). 2. Mandatory Cuts (Deal Fields in Kommo) Each metric must be filtered/grouped by: Client Citizenship (Kenya, Nigeria, India, etc.). Residence Status: lives in their country / expat (already in Europe). These are two different segments with different cycles, conversion rates, and checks. Country of Placement / Service: Poland, Serbia, Slovakia, Germany (ZAV). Manager, team, traffic channel, period. If any fields are missing in Kommo — the executor indicates which fields need to be added, the client adds them.3. Funnel and Leading Indicators Data by funnel, for each stage — summary and leading metrics: Traffic → lead: leads, CPL by channels + day-to-day expense/click dynamics. Lead → qualification: conversion + first response speed, touches/calls to the manager per day, unanswered leads. Qualification → contract/invoice: conversion + sent offers, stalled deals (days in stage above norm). Invoice → payment: payments, average check + unpaid invoices, failed payments. Summary: revenue, ROMI by channels, run rate to monthly plan. 4. Deal Cycle Average and median lead → payment cycle (business benchmark ~4 weeks), cycle trend over time. Breakdown of cycle by stages (how many days a deal sits at each stage) — to see which stage is dragging. List of deals that have stalled at a stage longer than normal. Cycle breakdown by segments: citizenship, residence status, country of placement, manager. 5. Early Warning of Decline (Key Block) Since the cycle is ~4 weeks, today's leads = payments in a month. The system must: Compare leads/qualifications of the current week with the moving average (4 weeks) and issue an alert if there is a downward deviation: “leads -X%, with a 4-week cycle expect a payment decline in the week [date].” Build payment forecast for 4 weeks ahead from the current pipeline: deals at each stage × historical conversion of the stage × remaining cycle. Highlight in red weeks where the forecast is below plan — with time to react. 6. Additional Payments and Sales Planning In the Kommo deal card, the date and amount of the planned additional payment are stored. The system must: Collect a calendar of upcoming additional payments: total expected, by weeks/months. Highlight overdue additional payments (date passed, no payments in Stripe) — a separate list for follow-up. Calculate the monthly plan as: plan − already paid − scheduled additional payments = how many new sales are needed (in money and in deal units at average check). Weekly schedule: additional payments + forecast of new payments against the weekly plan. 7. Manager Performance Daily snapshot for each manager: touches/calls, conversations, sent offers, payments — for each day separately, with a chart over the period. Progress on personal plan compared to monthly pace (ahead / on pace / behind). Benchmarking with colleagues. 8. Visualization and Roles “Traffic lights” (green/yellow/red) for key metrics relative to norms/plans; progress scales; trend graphs; mobile adaptive. Roles: CEO — everything; COO — entire funnel and managers; team lead — their team; manager — their metrics and position relative to colleagues. 9. Reports and AI Automated reports on schedule (daily summary, weekly report) in the dashboard and/or messenger. Free-form queries (“how has CPL from Meta changed over 2 weeks?”) — LLM over the repository. Alerts in the red zone and according to the rules from points 5–6. 10. Technical Expectations and Staging Repository (PostgreSQL/BigQuery or equivalent) + ETL: Kommo webhooks + periodic synchronization (15–60 min). Frontend: custom or BI tool — propose with justification; requirements for roles, traffic lights, forecasts, and AI queries must be implementable. Stages: (1) audit and metrics map → (2) MVP: Kommo + Stripe + Meta, funnel, traffic lights, roles → (3) deal cycle, early warning, additional payments and plan → (4) SEO, AI reports, alerts → (5) new advertising channels. Payment is staged, with a demo for each stage. In the response, indicate: similar projects (end-to-end analytics), stack with justification, timeline and cost estimates by stages, monthly ownership cost (hosting, tokens, licenses).